From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
Cc: | alvherre(at)commandprompt(dot)com, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_freespacemap question |
Date: | 2006-03-07 15:44:49 |
Message-ID: | 18884.1141746289@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2006-03-07 15:49:57 | current segfault if autovauum is on |
Previous Message | Tatsuo Ishii | 2006-03-07 15:37:44 | Re: pg_freespacemap question |
From | Date | Subject | |
---|---|---|---|
Next Message | Hans-Jürgen Schönig | 2006-03-07 16:58:58 | Re: CREATE SYNONYM ... |
Previous Message | Tatsuo Ishii | 2006-03-07 15:37:44 | Re: pg_freespacemap question |