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

Re: [PATCHES] pg_freespacemap question

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Mark Kirkwood <markir(at)paradise(dot)net(dot)nz>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>,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-13 13:44:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Mark Kirkwood wrote:
> Christopher Kings-Lynne wrote:
> >>The point here is that if tuples require 50 bytes, and there are 20
> >>bytes free on a page, pgstattuple counts 20 free bytes while FSM
> >>ignores the page.  Recording that space in the FSM will not improve
> >>matters, it'll just risk pushing out FSM records for pages that do
> >>have useful amounts of free space.
> >
> >Maybe an overloaded pgstattuple function that allows you to request FSM 
> >behavior?
> That's a nice idea - could also do equivalently by adding an extra 
> column "usable_free_space" or some such, and calculating this using FSM 
> logic.

The current pgstattuple function scans the whole table, so I don't think
this is a good idea.  Re: the overloaded function, I think the behaviors
are different enough to merit a separate function, with a different

Alvaro Herrera                      
The PostgreSQL Company - Command Prompt, Inc.

In response to

pgsql-hackers by date

Next:From: Jan de VisserDate: 2006-03-13 14:26:29
Subject: Re: [PERFORM] Hanging queries on dual CPU windows
Previous:From: Csaba NagyDate: 2006-03-13 10:22:07
Subject: Re: Where Can I Find The Code Segment For WAL Control?

pgsql-patches by date

Next:From: Sergey E. KoposovDate: 2006-03-13 13:53:47
Subject: Re: fix of some issues with multi-line query editing
Previous:From: Alvaro HerreraDate: 2006-03-13 13:42:12
Subject: Re: fix of some issues with multi-line query editing

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