From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
---|---|
To: | CR Lender <crlender(at)gmail(dot)com>, "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-03-26 18:28:54 |
Message-ID: | 1364322534.82496.YahooMailNeo@web162906.mail.bf1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
CR Lender <crlender(at)gmail(dot)com> wrote:
> According to the manual (9.1), pg_stat_get_last_vacuum_time() returns
>
> timestamptz | Time of the last non-FULL vacuum initiated by the
> | user on this table
>
> Why are full vacuums excluded from this statistic? It looks like there's
> no way to get the date of the last manual vacuum, if only full vacuums
> are performed.
Because FULL is a bit of a misnomer -- there are important things a
non-FULL vacuum does which a FULL vacuum does not. In general, a
VACUUM FULL should be followed by a non-FULL vacuum to keep the
database in good shape. Also, a VACUUM FULL is an extreme form of
maintenance which should rarely be needed; if you find that you
need to run VACUUM FULL, something is probably being done wrong
which should be fixed so that you don't need to continue to do such
extreme maintenance.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Moran | 2013-03-26 18:36:04 | Re: Unexpected behaviour of encode() |
Previous Message | Merlin Moncure | 2013-03-26 18:17:27 | Re: Unexpected behaviour of encode() |