Tom Lane wrote:
> With current CVS tip, I get an Assert() failure during initdb.
> #7 0x19268c in ExceptionalCondition (
> conditionName=0x76578 "!(TransactionIdIsCurrentTransactionId(tuple->t_xmax))
> ", exceptionP=0x4000a650, detail=0x0, fileName=0x401933ed "", lineNumber=202)
> at assert.c:73
> Any ideas?
Added --enable-cassert to my default configure switches.
Hmmm - with my latest changes I get the same, without them I
don't. Will backout the changes if I cannot find it quickly.
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
In response to
pgsql-hackers by date
|Next:||From: Chris Bitmead||Date: 2000-07-04 01:13:55|
|Subject: Re: [HACKERS] proposed improvements to PostgreSQL license|
|Previous:||From: Tom Lane||Date: 2000-07-04 00:47:18|
|Subject: Re: Fwd: Re: Fwd: Problem with recv syscall on socket when other side closed connection |
pgsql-committers by date
|Next:||From: Vadim B. Mikheev - CVS||Date: 2000-07-04 01:39:25|
|Subject: pgsql/src/backend/access/heap (heapam.c)|
|Previous:||From: Tom Lane||Date: 2000-07-04 00:11:22|
|Subject: Re: Re: [COMMITTERS] TOAST |