Re: pg_stat_get_last_vacuum_time(): why non-FULL?

From: CR Lender <crlender(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_stat_get_last_vacuum_time(): why non-FULL?
Date: 2013-04-09 11:47:37
Message-ID: 5163FFD9.50309@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2013-04-09 00:09, Kevin Grittner wrote:
> I'm not sure that what we're doing now is correct, but updating
> things as if a normal vacuum had been done would *not* be the thing
> to do. For starters, VACUUM FULL blows away the free space map and
> visibility map for a table. Among other things, that means that
> index-only scans will cease to work until the table has a normal
> vacuum.

Ah, now it makes sense. Thank you, that's what I was looking for.

And I agree with Jeff that this could be documented in more detail.

Thanks,
crl

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Christoph Berg 2013-04-09 12:44:12 Re: postgresql command line exploit found in the wild
Previous Message Christian Hammers 2013-04-09 11:28:10 Re: Queries seldomly take >4s while normally take <1ms?