Re: Assertion failure in new outer/semi/anti join code - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Assertion failure in new outer/semi/anti join code
Date
Msg-id 3379.1228695445@sss.pgh.pa.us
Whole thread Raw
In response to Assertion failure in new outer/semi/anti join code  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Gregory Stark <stark@enterprisedb.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


pgsql-hackers by date:

Previous
From: "Dmitry Koterov"
Date:
Subject: Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine
Next
From: Bruce Momjian
Date:
Subject: Re: ALTER composite type does not work, but ALTER TABLE which ROWTYPE is used as a type - works fine