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.
planagg.c (r1.51 -> r1.52)
pgsql-committers by date
|Next:||From: User Fxjr||Date: 2010-05-11 01:42:01|
|Subject: npgsql - Npgsql2: Changed line endings to Windows Format.|
|Previous:||From: User Mkz||Date: 2010-05-10 11:36:26|
|Subject: pgbouncer - pgbouncer: Clean warning flags for newer gccs.|