Thread: pgsql-server/src/backend/commands explain.c

CVSROOT:    /cvsroot
Module name:    pgsql-server
Changes by:    tgl@postgresql.org    03/02/10 12:06:23

Modified files:
    src/backend/commands: explain.c

Log message:
    Add code to show join rule (for outer and IN joins) in join type name.

Out of interest Tom, did you optimise the IN (huge list of scalars) case, or
is it just the IN (subselect) case?

Cheers,

Chris

> -----Original Message-----
> From: pgsql-committers-owner@postgresql.org
> [mailto:pgsql-committers-owner@postgresql.org]On Behalf Of Tom Lane
> Sent: Tuesday, 11 February 2003 1:06 AM
> To: pgsql-committers@postgresql.org
> Subject: [COMMITTERS] pgsql-server/src/backend/commands explain.c
>
>
> CVSROOT:    /cvsroot
> Module name:    pgsql-server
> Changes by:    tgl@postgresql.org    03/02/10 12:06:23
>
> Modified files:
>     src/backend/commands: explain.c
>
> Log message:
>     Add code to show join rule (for outer and IN joins) in join
> type name.
>
>
> ---------------------------(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:
> Out of interest Tom, did you optimise the IN (huge list of scalars) case, or
> is it just the IN (subselect) case?

Just IN (subselect).  AFAIK, IN (list of scalars) works reasonably well
already... at least for cases where the lefthand side is an indexed
column.  What problems are you concerned about?

            regards, tom lane

> Just IN (subselect).  AFAIK, IN (list of scalars) works reasonably well
> already... at least for cases where the lefthand side is an indexed
> column.  What problems are you concerned about?

Nothing in particular - I was just wondering how list of scalars performed
(as a huge list of OR'd scalars).  If it performs well, especially with an
index, then that's cool.

Chris