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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Better solution to the IN-list issue: instead of having an
Date: 2008-10-26 02:46:30
Message-ID: 20081026024630.5E63F7545A4@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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_3_STABLE

Modified Files:
--------------
pgsql/src/backend/parser:
parse_expr.c (r1.226.2.2 -> r1.226.2.3)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.226.2.2&r2=1.226.2.3)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-10-26 02:46:36 pgsql: Better solution to the IN-list issue: instead of having an
Previous Message Tom Lane 2008-10-26 02:46:25 pgsql: Better solution to the IN-list issue: instead of having an