pgsql: Better solution to the IN-list issue: instead of having an - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Better solution to the IN-list issue: instead of having an
Date
Msg-id 20081026024636.570AE7545A4@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Better solution to the IN-list issue: instead of having an arbitrary cutoff,
treat Var and non-Var IN-list items differently.  Only non-Var items are
candidates to go into an ANY(ARRAY) construct --- we put all Vars as separate
OR conditions on the grounds that that leaves more scope for optimization.
Per suggestion from Robert Haas.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/parser:
        parse_expr.c (r1.198.2.1 -> r1.198.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.198.2.1&r2=1.198.2.2)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Better solution to the IN-list issue: instead of having an
Next
From: jeremyd@pgfoundry.org (Jeremy Drake)
Date:
Subject: varint - varint: refactor operations on VarInts to functions with normal