| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add visibility map information to pg_freespace. |
| Date: | 2013-06-19 09:27:57 |
| Message-ID: | CA+U5nM+m0osdDWfxujxYCyrEmCie5nBcrUnMmR-2B1kiB+mXKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19 June 2013 10:15, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2013-06-19 10:03:40 +0100, Simon Riggs wrote:
>> On 19 June 2013 09:19, Kyotaro HORIGUCHI
>> <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>>
>> > It should useful in other aspects but it seems a bit complicated
>> > just to know about visibility bits for certain blocks.
>>
>> With your current patch you can only see the visibility info for
>> blocks in cache, not for all blocks. So while you may think it is
>> useful, it is also unnecessarily limited in scope.
>
> pg_freespace should do more than that? Are you thinking of
> pg_buffercache?
I was... my mistake. Please continue Kyotaro.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2013-06-19 09:55:09 | Re: Bugfix and new feature for PGXS |
| Previous Message | Andres Freund | 2013-06-19 09:15:14 | Re: Add visibility map information to pg_freespace. |