aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-05-10 16:25:46 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-05-10 16:25:46 +0000
commited83f6e38209016ae75832ae8997f190ea4a0c8e (patch)
tree5e516434a6cff602979a638b9ba16420f9267aa9 /src/backend/tcop/postgres.c
parent7fdbb8e3537c6baee61ff26e52e0923de15c6b3f (diff)
downloadpostgresql-ed83f6e38209016ae75832ae8997f190ea4a0c8e.tar.gz
postgresql-ed83f6e38209016ae75832ae8997f190ea4a0c8e.zip
When adding a "target IS NOT NULL" indexqual to the plan for an index-optimized
MIN or MAX, we must take care to insert the added qual in a legal place among the existing indexquals, if any. The btree index AM requires the quals to appear in index-column order. We didn't have to worry about this before because "target IS NOT NULL" was just treated as a plain scan filter condition; but as of 9.0 it can be an index qual and then it has to follow the rule. Per report from Ian Barwick.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions