Re: contrib/pg_stat_statements - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: contrib/pg_stat_statements
Date
Msg-id 48FC7F7D.6080205@enterprisedb.com
Whole thread Raw
In response to Re: contrib/pg_stat_statements  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander wrote:
> ITAGAKI Takahiro wrote:
>> Magnus Hagander <magnus@hagander.net> wrote:
>> I'm not sure what should be in the main and what should not.
>> Why is pg_freespacemap still in contrib?
> 
> I don't know, why is it? :-)

I guess that was a joke, given the smiley, but I'll bite:

1. pg_freespacemap is intimately tied to the implementation of the FSM. 
It was completely overhauled in the FSM rewrite, and there's no 
guarantee it won't change again in the future to reflect changes in the 
FSM implementation. And if it does, we won't bother to provide an easy 
upgrade path, so existing queries using it will brake. For the same 
reason it's in contrib and not pgFoundry: it's very dependent on the 
server version.

2. It's not useful for the general public.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pg_hba options parsing
Next
From: Tom Lane
Date:
Subject: Re: SSL cleanups/hostname verification