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

pgsql: Teach planner and executor to handle ScalarArrayOpExpr as an

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Teach planner and executor to handle ScalarArrayOpExpr as an
Date: 2005-11-25 19:47:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Teach planner and executor to handle ScalarArrayOpExpr as an indexable
qualification when the underlying operator is indexable and useOr is true.
That is, indexkey op ANY (ARRAY[...]) is effectively translated into an
OR combination of one indexscan for each array element.  This only works
for bitmap index scans, of course, since regular indexscans no longer
support OR'ing of scans.  There are still some loose ends to clean up
before changing 'x IN (list)' to translate as a ScalarArrayOpExpr;
for instance predtest.c ought to be taught about it.  But this gets the
basic functionality in place.

Modified Files:
        nodeBitmapIndexscan.c (r1.11 -> r1.12)
        nodeIndexscan.c (r1.106 -> r1.107)
        clausesel.c (r1.75 -> r1.76)
        indxpath.c (r1.193 -> r1.194)
        createplan.c (r1.203 -> r1.204)
        planagg.c (r1.11 -> r1.12)
        restrictinfo.c (r1.44 -> r1.45)
        selfuncs.c (r1.193 -> r1.194)
        nodeIndexscan.h (r1.24 -> r1.25)
        execnodes.h (r1.141 -> r1.142)
        paths.h (r1.88 -> r1.89)
        selfuncs.h (r1.25 -> r1.26)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-11-26 03:03:07
Subject: pgsql: Change seqscan logic so that we check visibility of all tuples on
Previous:From: User DpageDate: 2005-11-25 11:58:45
Subject: pginstaller - pginst: Check for the version of Python that we actually

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