From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
---|---|
To: | Bernd Helmle <mailings(at)oopsware(dot)de> |
Cc: | Greg Smith <greg(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Measuring relation free space |
Date: | 2011-11-07 04:55:48 |
Message-ID: | 4EB764D4.8040702@catalyst.net.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 07/11/11 10:20, Bernd Helmle wrote:
>
>
> --On 6. November 2011 01:08:11 -0200 Greg Smith <greg(at)2ndQuadrant(dot)com>
> wrote:
>
>> Attached patch adds a new function to the pageinspect extension for
>> measuring
>> total free space, in either tables or indexes.
>
> I wonder if that should be done in the pgstattuple module, which
> output some similar numbers.
>
Not meaning to disparage Greg's effort in any way, but I was thinking
the same thing about pg_freespacemap. I have not checked what - if any
differences there are in output, but it would be interesting to compare
which of the various (3 at present) extensions with slightly overlapping
areas of functionality should perhaps be merged.
I am guessing (at this point very much guessing) that pg_freespace map
may return its data faster, as pageinspect is gonna have to grovel
through all the pages for itself (whereas pg_freespacemap relies on
using info from the ... free space map fork).
regards
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Kundrát | 2011-11-07 05:02:27 | [patch] Include detailed information about a row failing a CHECK constraint into the error message |
Previous Message | J Smith | 2011-11-07 03:25:33 | Re: unaccent extension missing some accents |