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

Re: ANALYZE versus expression indexes with nondefault opckeytype

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ANALYZE versus expression indexes with nondefault opckeytype
Date: 2010-07-31 15:46:52
Message-ID: F1EF7141-983B-496A-992E-4A31B2B347CF@gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Jul 31, 2010, at 11:00 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It's only been very recently that we had any useful stats capability
> that could apply in such situations (in fact I think we still haven't
> actually shipped a non-bogus version of tsvector typanalyze :-().
> So I'm not sure anyone would have realized they were missing something.
> But it would be nice to have this working in 8.4, and I'll be quite
> unhappy if we don't have it in 9.0.
> 
> If people feel it's not too late for an ABI break in 9.0 then I'm
> willing to compromise on backpatching the "clean" fix.  I'm not entirely
> convinced it's that much cleaner than the hack solution though.

I think this whole discussion is starting with the wrong premise. This is not a bug fix; therefore, it's 9.1 material.  If anyone else had suggested slipping this into 9.0, let alone 8.4, we would have punted it in a heartbeat.

...Robert


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-07-31 16:02:15
Subject: Re: rbtree code breaks GIN's adherence to maintenance_work_mem
Previous:From: Tom LaneDate: 2010-07-31 15:00:19
Subject: Re: ANALYZE versus expression indexes with nondefault opckeytype

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