| From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FSM rewrite committed, loose ends |
| Date: | 2008-10-01 00:44:43 |
| Message-ID: | 65937bea0809301744o4d239709p8ac764297d936b82@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 30, 2008 at 5:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> writes:
> > I vote for contrib/pg_freespacemap functions to be included in the core
> > since FSM is in core.
>
> The old FSM was in core, too. That's not a helpful argument.
In the absence of these functions, one has to run VACUUM just to be able to
see the freespace information; putting these functions in contrib/ is just
asking for extra work from DBAs, who IMHO are not very comfortable with
'make; make install'.
If a feature is mainstream, so should be the functions to extract
information about it.
Best regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | indiatimes | yahoo }.com
EnterpriseDB http://www.enterprisedb.com
Mail sent from my BlackLaptop device
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2008-10-01 00:59:37 | Re: Common Table Expressions (WITH RECURSIVE) patch |
| Previous Message | Simon Riggs | 2008-09-30 22:52:31 | Infrastructure changes for recovery (v8) |