Postgres Pro
Downloads
Home   >   mailing lists

Re: Add visibility map information to pg_freespace. - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Add visibility map information to pg_freespace.
Date
Msg-id CA+U5nMLuDoYcsMGUZQsEji9LYOOgLnzg+gpASnbAi_EnOqt3UA@mail.gmail.com
Whole thread Raw
In response to Re: Add visibility map information to pg_freespace.  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Add visibility map information to pg_freespace.  (Andres Freund <andres@2ndquadrant.com>)
Re: Add visibility map information to pg_freespace.  (Satoshi Nagayasu <snaga@uptime.jp>)
List pgsql-hackers
Tree view 
On 19 June 2013 09:19, Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.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

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: GIN improvements part2: fast scan
Next
From: Andres Freund
Date:
Subject: Re: Add visibility map information to pg_freespace.