Re: pg_stat_get_last_vacuum_time(): why non-FULL? - Mailing list pgsql-general

From CR Lender
Subject Re: pg_stat_get_last_vacuum_time(): why non-FULL?
Date
Msg-id 5163FFD9.50309@gmail.com
Whole thread Raw
In response to Re: pg_stat_get_last_vacuum_time(): why non-FULL?  (Kevin Grittner <kgrittn@ymail.com>)
List 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


pgsql-general by date:

Previous
From: Christian Hammers
Date:
Subject: Re: Queries seldomly take >4s while normally take <1ms?
Next
From: Christoph Berg
Date:
Subject: Re: postgresql command line exploit found in the wild