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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <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 14:25:29
Message-ID: 20968.1300717529@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Mar 21, 2011 at 7:17 AM, Marti Raudsepp <marti(at)juffo(dot)org> wrote:
>> I know that the Merge Append patch required some changes in the
>> min/max optimization, which is probably the cause.

> Yeah, I think this is a direct result of commit
> 034967bdcbb0c7be61d0500955226e1234ec5f04.

Yeah, looks that way. I'm not sure what it would take to re-support
this case without losing the other advantages of the change. Personally
I'm not terribly excited about it: I don't think that suppressing nulls
from an index this way is really very useful. Using a partial index
probably eats more planner cycles than you'll save, overall.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message rsmogura 2011-03-21 15:24:22 Re: 2nd Level Buffer Cache
Previous Message Tom Lane 2011-03-21 14:18:50 Re: Rectifying wrong Date outputs