Re: Planner regression in 9.1: min(x) cannot use partial index with NOT NULL

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: robertmhaas(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, marti(at)juffo(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Planner regression in 9.1: min(x) cannot use partial index with NOT NULL
Date: 2011-03-21 17:34:11
Message-ID: AANLkTi=zBMY2F=WH+BsDpoPGjoCgwTVUb8yMm+gJuh0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

So it's a clever hack that we used to allow the partial indexes to be
used. It relied on the implicit assumption that min(x) and max(x)
where the only values of x where NULL were both NULL.

It would be nice if we were clever enough to support *any* strict
aggregate using partial indexes on WHERE NOT NULL since they'll all
have that property.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-03-21 17:40:41 Re: Planner regression in 9.1: min(x) cannot use partial index with NOT NULL
Previous Message Tom Lane 2011-03-21 17:14:33 Re: Planner regression in 9.1: min(x) cannot use partial index with NOT NULL