Thread: pgsql: Fix "cannot handle unplanned sub-select" error that can occur
pgsql: Fix "cannot handle unplanned sub-select" error that can occur
From
tgl@postgresql.org (Tom Lane)
Date:
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_0_STABLE Modified Files: -------------- pgsql/src/backend/optimizer/util: var.c (r1.63 -> r1.63.4.1) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/var.c?r1=1.63&r2=1.63.4.1) pgsql/src/test/regress/expected: subselect.out (r1.10.4.3 -> r1.10.4.4) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/subselect.out?r1=1.10.4.3&r2=1.10.4.4) pgsql/src/test/regress/sql: subselect.sql (r1.7.4.1 -> r1.7.4.2) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/subselect.sql?r1=1.7.4.1&r2=1.7.4.2)