Skip site navigation (1) Skip section navigation (2)

Re: pg_freespacemap question

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, alvherre(at)commandprompt(dot)com, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_freespacemap question
Date: 2006-03-09 04:12:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:
> Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> writes:
>>>Good points! I had not noticed this test case. Probably NULL is better 
>>Would setting it to 'BLCKSZ - (fixed index header stuff)' be better, 
> No, I don't think so, because that will just make it harder to recognize
> what's what (remember that BLCKSZ isn't really a constant, and the index
> overhead is not the same for all AMs either).  The point here is that
> for indexes the FSM tracks whole-page availability, not the amount of
> free space within pages.  So I think NULL is a reasonable representation
> of that.  Using NULL will make it easy to filter the results if you want
> to see only heap-page data or only index-page data, whereas it will be
> very hard to do that if the view adopts an ultimately-artificial
> convention about the amount of available space on an index page.

Right - after suggesting it I realized that coding the different index
overhead for each possible AM would have been ... difficult :-). A patch
is attached to implement the NULL free bytes and other recommendations:

1/ Index free bytes set to NULL
2/ Comment added to the README briefly mentioning the index business
3/ Columns reordered more logically
4/ 'Blockid' column removed
5/ Free bytes column renamed to just 'bytes' instead of 'blockfreebytes'

Now 5/ was only hinted at, but seemed worth doing while I was there
(hopefully I haven't made it too terse now....).



Attachment: pg_freespacemap.patch
Description: text/plain (12.9 KB)

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-03-09 04:14:09
Subject: Re: [COMMITTERS] pgsql: Remove Christof Petig copyright on include file, per author
Previous:From: Marc G. FournierDate: 2006-03-09 03:27:33
Subject: Re: [COMMITTERS] pgsql: Remove Christof Petig copyright

pgsql-patches by date

Next:From: ITAGAKI TakahiroDate: 2006-03-09 06:52:18
Subject: Re: Automatic free space map filling
Previous:From: Jim C. NasbyDate: 2006-03-09 02:16:12
Subject: Re: [PATCHES] Add switches for DELIMITER and NULL in pg_dump COPY

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group