Re: assertion failure 9.3.4

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: assertion failure 9.3.4
Date: 2014-04-15 02:02:10
Message-ID: 20140415020210.GH5822@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-04-15 02:06:12 Re: API change advice: Passing plan invalidation info from the rewriter into the planner?
Previous Message Peter Eisentraut 2014-04-15 01:54:46 Re: tests for client programs