Re: pg_freespacemap question - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_freespacemap question
Date
Msg-id 18884.1141746289@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_freespacemap question  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Responses Re: pg_freespacemap question  (Mark Kirkwood <markir@paradise.net.nz>)
List pgsql-hackers
Tatsuo Ishii <ishii@sraoss.co.jp> writes:
>> Peter Eisentraut wrote:
>> I have another question -- why is the view showing relfilenode and
>> reltablespace?  I imagine it should be showing the relation Oid instead.

> I guess that's because FSM keeps those info, not relation oid.

Right, which is correct because free space is associated with physical
files not logical relations.  (TRUNCATE, CLUSTER, etc will completely
change the freespace situation for a rel, but they don't change its OID.)

I do agree with the comment that the column order seems nonintuitive;
I'd expect database/tablespace/relfilenode/blocknumber, or possibly
tablespace first.  The names used for the columns could do with
reconsideration.  And I don't see the point of the blockid column at
all.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: pg_freespacemap question
Next
From: Tatsuo Ishii
Date:
Subject: current segfault if autovauum is on