From: Amit Kapila <amit.kapila@huawei.com>
To: 'Josh Berkus' <josh@agliodbs.com>
To: pgsql-hackers@postgresql.org
Subject: Re: 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL
Date: Thu, 10 Jan 2013 11:45:47 +0530
Message-ID: <006901cdeef9$eefd56a0$ccf803e0$@kapila@huawei.com> (raw)
In-Reply-To: <50EE0D8C.3080602@agliodbs.com>
References: <20130109230731.GA30885@momjian.us>
<50EE0D8C.3080602@agliodbs.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Thursday, January 10, 2013 6:09 AM Josh Berkus wrote:
> On 01/09/2013 03:07 PM, Bruce Momjian wrote:
> > How do we want to handle the case where VACUUM FULL clears the
> > visibility map, causing loss of index-only scans?
> >
> > http://archives.postgresql.org/pgsql-performance/2012-
> 11/msg00317.php
> >
> > Do we document this behavior or add a TODO item?
> >
>
> Both?
>
> Surely VACUUM FULL should rebuild the visibility map, and make tuples
> in
> the new relation all-visible, no?
I think it cannot made all visible.
How about if any transaction in SSI mode is started before Vacuum Full, should it see all tuples.
With Regards,
Amit Kapila.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: amit.kapila@huawei.com, josh@agliodbs.com
Subject: Re: 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL
In-Reply-To: <006901cdeef9$eefd56a0$ccf803e0$@kapila@huawei.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox