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

pgsql: When adding a "target IS NOT NULL" indexqual to the plan for an

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: When adding a "target IS NOT NULL" indexqual to the plan for an
Date: 2010-05-10 16:25:46
Message-ID: 20100510162546.903347541D2@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
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.

Modified Files:
--------------
    pgsql/src/backend/optimizer/plan:
        planagg.c (r1.51 -> r1.52)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planagg.c?r1=1.51&r2=1.52)

pgsql-committers by date

Next:From: User FxjrDate: 2010-05-11 01:42:01
Subject: npgsql - Npgsql2: Changed line endings to Windows Format.
Previous:From: User MkzDate: 2010-05-10 11:36:26
Subject: pgbouncer - pgbouncer: Clean warning flags for newer gccs.

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