| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: a fast bloat measurement tool (was Re: Measuring relation free space) |
| Date: | 2015-02-26 00:56:37 |
| Message-ID: | 54EE6F45.2020502@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 26/02/15 13:32, Simon Riggs wrote:
> On 25 February 2015 at 23:30, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>
>> That said, I don't want to block this; I think it's useful. Though, perhaps
>> it would be better as an extension instead of in contrib? I don't think it
>> should be very version dependent?
>
> The whole point of this is to get it into contrib.
>
> It could have published it as an extension months ago.
>
Is this intended to replace pg_freespacemap? Not trying to be
overprotective or anything :-) but is this new extension/module
better/faster/stronger/more accurate etc? If so then excellent! Ohth was
wondering if people either a) didn't know about pg_freespacemap or b)
consider that it is crap and won't use it.
Cheers
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-02-26 01:04:39 | Re: a fast bloat measurement tool (was Re: Measuring relation free space) |
| Previous Message | David Steele | 2015-02-26 00:54:28 | Re: collations in shared catalogs? |