Re: FailedAssertion() in 8.2beta1 - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: FailedAssertion() in 8.2beta1
Date
Msg-id 87k63c3ozx.fsf@enterprisedb.com
Whole thread Raw
In response to Re: FailedAssertion() in 8.2beta1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.us> writes:

> "Sergey E. Koposov" <math@sai.msu.ru> writes:
>> I've found a bug with 8.2beta1:
>
> Can you put together a self-contained test case for this?  The planner
> is evidently generating an incorrect plan from that messy view, but
> trying to reverse-engineer the complete scenario from what you've told
> us looks painful.  (No, I don't think the log setting is related.)

Would a core dump file (and his binary) be useful?


Earlier I was going to suggest he execute these commands from gdb:
f 5p *rtentryp *estate

But I fear even that won't be enough to actually track down where the state
got corrupted.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Select for update with outer join broken?
Next
From: Tom Lane
Date:
Subject: Re: FailedAssertion() in 8.2beta1