Re: Assertion failure in new outer/semi/anti join code

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Postgres <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assertion failure in new outer/semi/anti join code
Date: 2008-12-08 00:17:25
Message-ID: 3379.1228695445@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> The following query causes an assertion failure on CVS head:

> SELECT * FROM (SELECT 1 AS i) AS a WHERE NOT EXISTS (SELECT 1 WHERE 1 <> i);

Fixed, thanks for the report.

> Looks like it's assuming there's at least one relation on each side of the
> join.

Yeah. I don't think we can remove that assumption easily; best to just
not try to optimize this case.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-12-08 00:57:48 Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine
Previous Message Gevik Babakhani 2008-12-07 23:50:08 Re: BUG #4186: set lc_messages does not work