Re: Stats for inheritance trees - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Stats for inheritance trees
Date
Msg-id 603c8f070912291817m4ae2658chf64aafdff09ea8d9@mail.gmail.com
Whole thread Raw
In response to Re: Stats for inheritance trees  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Stats for inheritance trees  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Dec 29, 2009 at 9:12 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Yep.  It would also lower the barrier to future innovations of that
>> type, which would be a good thing, IMO.  Unfortunately we'd likely
>> need to continue to support the existing syntax at least for
>> attstattarget, which is kind of a bummer, but seems managable.  I
>> think we could throw over the syntax for ALTER TABLE ... ADD
>> STATISTICS DISTINCT since it is an 8.5-ism.
>
> Yeah --- if we think we might want to do this, now is the time,
> before we're stuck with supporting that syntax.  (I was thinking
> earlier today that attdistinct was already in 8.4, but it's not.)

If you'd be willing to look over the latest version of my
per-tablespace random_page_cost/seq_page_cost patch, which I posted to
-hackers some time in the last few days, I can get that committed and
then start working on this, if you'd like.

...Robert


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PATCH: Add hstore_to_json()
Next
From: Daniel Farina
Date:
Subject: Re: [PATCH 4/4] Add tests to dblink covering use of COPY TO FUNCTION