pgsql: Fix another problem in 8.2 changes that allowed "one-time" qual

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix another problem in 8.2 changes that allowed "one-time" qual
Date: 2007-02-16 03:49:10
Message-ID: 20070216034910.EDC799FBD36@postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix another problem in 8.2 changes that allowed "one-time" qual conditions to
be checked at plan levels below the top; namely, we have to allow for Result
nodes inserted just above a nestloop inner indexscan. Should think about
using the general Param mechanism to pass down outer-relation variables, but
for the moment we need a back-patchable solution. Per report from Phil Frost.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
pgsql/src/backend/executor:
nodeResult.c (r1.34.2.3 -> r1.34.2.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeResult.c.diff?r1=1.34.2.3&r2=1.34.2.4)
pgsql/src/backend/optimizer/plan:
setrefs.c (r1.126 -> r1.126.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.126&r2=1.126.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2007-02-16 03:50:29 pgsql: Remove tabs from SGML files to help tag alingment and improve
Previous Message Tom Lane 2007-02-16 03:49:04 pgsql: Fix another problem in 8.2 changes that allowed "one-time" qual