pgsql: Fix an oversight in join-removal optimization: we have to check - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix an oversight in join-removal optimization: we have to check
Date
Msg-id 20100322135716.4A93E7541D0@cvs.postgresql.org
Whole thread Raw
Responses Re: pgsql: Fix an oversight in join-removal optimization: we have to check
List pgsql-committers
Log Message:
-----------
Fix an oversight in join-removal optimization: we have to check not only for
plain Vars that are generated in the inner rel and used above the join, but
also for PlaceHolderVars.  Per report from Oleg K.

Modified Files:
--------------
    pgsql/src/backend/optimizer/path:
        joinpath.c (r1.130 -> r1.131)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/joinpath.c?r1=1.130&r2=1.131)
    pgsql/src/test/regress/expected:
        join.out (r1.43 -> r1.44)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/join.out?r1=1.43&r2=1.44)
    pgsql/src/test/regress/sql:
        join.sql (r1.32 -> r1.33)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/join.sql?r1=1.32&r2=1.33)

pgsql-committers by date:

Previous
From: meskes@postgresql.org (Michael Meskes)
Date:
Subject: pgsql: Fixed ECPG regression test to make sure it uses absolute paths
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Re-order createuser and vacuumedb documentation options, for