Andrew Dunstan wrote: > and here the stack trace: > > #0 0x000000361ba36285 in __GI_raise (sig=6) at > ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x000000361ba37b9b in __GI_abort () at abort.c:91 > #2 0x000000000075c157 in ExceptionalCondition > (conditionName=<optimized out>, errorType=<optimized out>, > fileName=<optimized out>, lineNumber=<optimized out>) > at /home/andrew/pgl/pg_9_3/src/backend/utils/error/assert.c:54 > #3 0x000000000048c2af in MultiXactIdGetUpdateXid (xmax=<optimized > out>, t_infomask=<optimized out>) at > /home/andrew/pgl/pg_9_3/src/backend/access/heap/heapam.c:5873 > #4 0x000000000078ad50 in HeapTupleSatisfiesMVCC > (tuple=0x7feb3be8a790, snapshot=0x1025d70, buffer=2172) at > /home/andrew/pgl/pg_9_3/src/backend/utils/time/tqual.c:1221
Clearly this is a bug related to multixacts and the related tqual.c changse. Will look. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
