Re: FSM rewrite committed, loose ends - Mailing list pgsql-hackers

From Dave Page
Subject Re: FSM rewrite committed, loose ends
Date
Msg-id 937d27e10809300700w2277d4bbu624308fbbc245f90@mail.gmail.com
Whole thread Raw
In response to Re: FSM rewrite committed, loose ends  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: FSM rewrite committed, loose ends  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, Sep 30, 2008 at 2:53 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:

>> For convenience, would it be possible to see about having all this
>> provided by PostgreSQL?
>>  a. pg_relation_size()
>>  b. pg_relation_toast_size()
>>  c. pg_relation_fsm_size()
>>  d. pg_relation_indexes_size()
>>  e. pg_total_relation_size() = a + b + c + d
>>
>> Are there some other things to add in the mix?
>
> Should pg_relation_indexes_size() include the FSMs of the indexes? Should
> pg_relation_toast_size() include the toast index and FSM as well?

It might be worth revisiting the near identical discussions we had
when Andreas & I integrated this stuff into the backend for 8.1.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: FSM rewrite committed, loose ends
Next
From: Heikki Linnakangas
Date:
Subject: Re: Index size increases after VACUUM FULL