From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix "cannot handle unplanned sub-select" error that can occur |
Date: | 2010-07-08 00:14:10 |
Message-ID: | 20100708001410.ECA287541D4@cvs.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Fix "cannot handle unplanned sub-select" error that can occur when a
sub-select contains a join alias reference that expands into an expression
containing another sub-select. Per yesterday's report from Merlin Moncure
and subsequent off-list investigation.
Back-patch to 7.4. Older versions didn't attempt to flatten sub-selects in
ways that would trigger this problem.
Tags:
----
REL8_4_STABLE
Modified Files:
--------------
pgsql/src/backend/optimizer/util:
var.c (r1.86 -> r1.86.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/var.c?r1=1.86&r2=1.86.2.1)
pgsql/src/test/regress/expected:
subselect.out (r1.22.2.1 -> r1.22.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/subselect.out?r1=1.22.2.1&r2=1.22.2.2)
pgsql/src/test/regress/sql:
subselect.sql (r1.14.2.1 -> r1.14.2.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/subselect.sql?r1=1.14.2.1&r2=1.14.2.2)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-07-08 00:14:16 | pgsql: Fix "cannot handle unplanned sub-select" error that can occur |
Previous Message | Tom Lane | 2010-07-08 00:14:04 | pgsql: Fix "cannot handle unplanned sub-select" error that can occur |