pgsql: Back out prior patch and instead just suppress SubqueryScan - Mailing list pgsql-committers

From tgl@svr1.postgresql.org (Tom Lane)
Subject pgsql: Back out prior patch and instead just suppress SubqueryScan
Date
Msg-id 20050905185938.5DF29D7B28@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Back out prior patch and instead just suppress SubqueryScan elimination
when there are extra resjunk columns in the child node.  I found some
additional cases involving Append nodes that weren't handled by the
prior patch, and it's not clear how to fix them in the same way without
breaking inheritance cases.  So the prudent path seems to be to narrow
the scope of the optimization.

Modified Files:
--------------
    pgsql/src/backend/optimizer/plan:
        setrefs.c (r1.113 -> r1.114)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.113&r2=1.114)

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Conditionally output the server version number in psql if it
Next
From: tgl@svr1.postgresql.org (Tom Lane)
Date:
Subject: pgsql: Implement a preliminary 'template' facility for procedural