Re: Assertion failure in REL9_5_STABLE
От | Alvaro Herrera |
---|---|
Тема | Re: Assertion failure in REL9_5_STABLE |
Дата | |
Msg-id | 20160817160449.GA896907@alvherre.pgsql обсуждение исходный текст |
Ответ на | Assertion failure in REL9_5_STABLE (Marko Tiikkaja <marko@joh.to>) |
Список | pgsql-hackers |
Marko Tiikkaja wrote: > Running one specific test from our application against REL9_5_STABLE > (current as of today) gives me this: > > #2 0x00007effb59595be in ExceptionalCondition ( > conditionName=conditionName@entry=0x7effb5b27a88 "!(CritSectionCount > 0 > || TransactionIdIsCurrentTransactionId(( (!((tup)->t_infomask & 0x0800) && > ((tup)->t_infomask & 0x1000) && !((tup)->t_infomask & 0x0080)) ? > HeapTupleGetUpdateXid(tup) : ( (tup)-"..., > errorType=errorType@entry=0x7effb599b74b "FailedAssertion", > fileName=fileName@entry=0x7effb5b2796c "combocid.c", > lineNumber=lineNumber@entry=132) at assert.c:54 > #3 0x00007effb598e19b in HeapTupleHeaderGetCmax (tup=0x7effa85714c8) at > combocid.c:131 Can you please do frame 3 print tup->t_ctid in gdb? That would print the tuple address with which to grep the xlog sequence. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: