Re: ANALYZE versus expression indexes with nondefault opckeytype

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <robertmhaas(at)gmail(dot)com>,<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>,<sfrost(at)snowman(dot)net>
Subject: Re: ANALYZE versus expression indexes with nondefault opckeytype
Date: 2010-07-31 19:26:56
Message-ID: 4C5432B00200002500033F90@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas 07/31/10 12:33 PM >>>
> Tom Lane wrote:
>> Robert Haas writes:
>>> I think this whole discussion is starting with the wrong premise.
>>> This is not a bug fix; therefore, it's 9.1 material.
>>
>> Failing to store stats isn't a bug?
>
> Well, it kind of sounds more like you're removing a known
> limitation than fixing a bug.

It's operating as designed and documented. There is room for
enhancement, but the only thing which could possibly justify this as
9.0 material is if there was a demonstrated performance regression in
9.0 for which this was the safest cure.

-Kevin

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-08-01 01:11:53 Re: review patch: Distinguish between unique indexes and unique constraints
Previous Message Robert Haas 2010-07-31 17:40:36 Re: review: xml_is_well_formed