Thread: pgsql/src/backend/optimizer/plan planner.c

CVSROOT:    /cvsroot
Module name:    pgsql
Changes by:    tgl@postgresql.org    02/06/13 11:10:25

Modified files:
    src/backend/optimizer/plan: planner.c

Log message:
    Make WHERE conditions pulled up from subqueries be executed before outer
    WHERE conditions, if there is no reason to do it differently.

Just out of interest - why is that better?

Chris

> -----Original Message-----
> From: pgsql-committers-owner@postgresql.org
> [mailto:pgsql-committers-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Thursday, 13 June 2002 11:10 PM
> To: pgsql-committers@postgresql.org
> Subject: [COMMITTERS] pgsql/src/backend/optimizer/plan planner.c
>
>
> CVSROOT:    /cvsroot
> Module name:    pgsql
> Changes by:    tgl@postgresql.org    02/06/13 11:10:25
>
> Modified files:
>     src/backend/optimizer/plan: planner.c
>
> Log message:
>     Make WHERE conditions pulled up from subqueries be executed
> before outer
>     WHERE conditions, if there is no reason to do it differently.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>

"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> Just out of interest - why is that better?

See Mike Mascari's recent gripes about functions and views.
This is a pretty weak security improvement, but not a negligible
one.

            regards, tom lane