| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, markir(at)paradise(dot)net(dot)nz, 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-13 03:29:44 |
| Message-ID: | 4414E728.6080103@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> 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?
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2006-03-13 04:37:00 | Re: [PATCHES] pg_freespacemap question |
| Previous Message | Tom Lane | 2006-03-13 03:15:07 | Re: [PATCHES] pg_freespacemap question |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-13 04:24:35 | Re: fix of some issues with multi-line query editing |
| Previous Message | Tom Lane | 2006-03-13 03:15:07 | Re: [PATCHES] pg_freespacemap question |