Skip site navigation (1) Skip section navigation (2)

Re: Segfaults and assertion failures with not too extraordinary views and queries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Phil Frost <phil(at)macprofessionals(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Segfaults and assertion failures with not too extraordinary views and queries
Date: 2007-02-15 03:13:56
Message-ID: 14977.1171509236@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
I wrote:
> Hm, I see the assert failure, but this example doesn't seem to crash
> when asserts are off, and I'd not expect it to: it should either work or
> elog(ERROR) in ExecRestrPos.  So maybe you've found more than one issue.

The attached patch fixes the failure you exhibited, but I still don't
see how this problem would lead to a non-assert crash --- what you
should get is elog(ERROR, "unrecognized node type") from ExecRestrPos.
So please try some more test cases and see if there's another problem
lurking.

BTW, the problem was due to code added in response to an earlier gripe of
yours (allowing gating conditions to be pushed further down in the join
tree).  Maybe you're the only person stressing that particular aspect
of the planner ...

			regards, tom lane


Attachment: result-mark-82.patch
Description: application/octet-stream (4.0 KB)

In response to

Responses

pgsql-bugs by date

Next:From: Pelle JohanssonDate: 2007-02-15 09:55:48
Subject: BUG #3012: Wrong JOIN order when a JOIN depends on result from a LEFT JOIN.
Previous:From: Tom LaneDate: 2007-02-14 22:49:16
Subject: Re: Segfaults and assertion failures with not too extraordinary views and queries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group