On Wed, 2008-10-22 at 13:25 -0400, Tom Lane wrote:
> #5 0x171680 in TransactionIdSetStatusBit (xid=2063810256,
> status=2063810248,
> lsn={xlogid = 0, xrecoff = 0}, slotno=0) at clog.c:330
> #6 0x1714e8 in TransactionIdSetPageStatus (xid=84, nsubxids=1,
> subxids=0x4008dd78, status=2063840993, lsn={xlogid = 0, xrecoff =
> 0},
> pageno=0) at clog.c:290
> #7 0x1712dc in TransactionIdSetTreeStatus (xid=19394, nsubxids=1,
> subxids=0x4008dd78, status=1, lsn={xlogid = 0, xrecoff = 0}) at
> clog.c:204
> #8 0x1722f8 in TransactionIdCommitTree (xid=2063670312,
> nxids=2063839972,
> xids=0x7b011cf0) at transam.c:266
> #9 0x1785b8 in xact_redo_commit (xlrec=0x4008dd48, xid=19394) at
> xact.c:4222
These traces look weird. Look at the way the xid changes value as we
move from call to call. It looks like something is screwy there. If
those values are correct we should have failed an earlier assertion.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
