| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | 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:03:40 |
| Message-ID: | CA+U5nMLuDoYcsMGUZQsEji9LYOOgLnzg+gpASnbAi_EnOqt3UA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Let's just have something that is easy to use that lets us see the
visibility state for a block, not just blocks in freespace.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-06-19 09:15:14 | Re: Add visibility map information to pg_freespace. |
| Previous Message | Alexander Korotkov | 2013-06-19 08:56:37 | Re: GIN improvements part2: fast scan |