Skip site navigation (1) Skip section navigation (2)

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:25
Message-ID: 20081026024625.395637545A4@cvs.postgresql.org (view raw or flat)
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.

Modified Files:
--------------
    pgsql/src/backend/parser:
        parse_expr.c (r1.236 -> r1.237)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.236&r2=1.237)

pgsql-committers by date

Next:From: Tom LaneDate: 2008-10-26 02:46:30
Subject: pgsql: Better solution to the IN-list issue: instead of having an
Previous:From: Tom LaneDate: 2008-10-25 19:51:32
Subject: pgsql: Be a little smarter about qual handling for semi-joins: a qual

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group