-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoupdate broken:insert cause backend segment fault #20
Comments
Sorry, I can not reproduce the problem: cs_create(1 row) postgres=# insert into test_trig2 values(now(),'123','456'); Can you try it once more with some other table, for example test_trig22? |
wired,I can reproduce it realiable,this is the gdb stack: Program received signal SIGSEGV, Segmentation fault. the suspension code is: I try to create new database with SQL_ASCII encoding instead of UTF-8、create new database、compile new code,but the segment always happened. |
some more info: and more intresting is here: test3=# insert into test_trig2 values(now()::timestamp,'123'::char(10),'456'::char(10)); test3=# select * from test_trig2 ; test3=# select * from test_trig2_get(); test3=# insert into test_trig2 values(now()::timestamp,'123'::char(10),'456'::char(10)); So the auto load is OK,but When the CS is loaded,the insert will failed with: data format was changed;but if the CS is not loaded,the insert will cause segment. more debug info: this: |
Still can not reproduce the problem... |
Can you also point me on IMCS parameters you are using. |
the patched version of imcs--1.1.sql solve the problem! this is my settings: |
create table test_trig2(ts timestamp,v char(10),v2 char(10));
select cs_create('test_trig2','ts',autoupdate:=true);
insert into test_trig2 values(now(),'123','456');
The connection to the server was lost. Attempting reset: Failed.
!> \q
The text was updated successfully, but these errors were encountered: