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

Re: [PATCHES] pg_freespacemap question

From: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
To: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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: [PATCHES] pg_freespacemap question
Date: 2006-03-19 23:33:33
Message-ID: 441DEA4D.9000804@paradise.net.nz (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Mark Kirkwood wrote:
> Tom Lane wrote:
> 
>>
>> I do notice a rather serious shortcoming of pg_freespacemap in its
>> current incarnation, which is that it *only* shows you the per-page free
>> space data, and not any of the information that would let you determine
>> what the FSM is doing to filter the raw data.  The per-relation
>> avgRequest and lastPageCount fields would be interesting for instance.
>> Perhaps there should be a second view with one row per relation to
>> carry the appropriate data.
>>
> 
> Ok - I did wonder about 2 views, but was unsure if the per-relation 
> stuff was interesting. Given that it looks like it is interesting, I'll 
> see about getting a second view going.
> 

This patch implements the second view for FSM relations. I have renamed 
the functions and views to be:

pg_freespacemap_relations
pg_freespacemap_pages

This patch depends on the previous one (which was called simply 
'pg_freespacemap.patch').

Cheers

Mark

Attachment: pg_freespacemap-1.patch.gz
Description: application/gzip (4.8 KB)

In response to

Responses

pgsql-hackers by date

Next:From: Jan CruzDate: 2006-03-20 02:35:24
Subject: Re: suggestion
Previous:From: Devrim GUNDUZDate: 2006-03-19 23:08:26
Subject: Re: [HACKERS] PostgreSQL Anniversary Proposals --

pgsql-patches by date

Next:From: Mark KirkwoodDate: 2006-03-19 23:39:18
Subject: Pg_buffercache tidy
Previous:From: Andreas PflugDate: 2006-03-19 11:22:45
Subject: Re: Automatically setting work_mem

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