From: Kevin Grittner <kgrittn@ymail.com>
To: Eoin O'Hehir <eoin.ohehir@clavisinsight.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Does VACUUM FULL need ANALYZE ?
Date: Fri, 26 Jun 2015 19:40:18 +0000 (UTC)
Message-ID: <76082180.506975.1435347618922.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <CAMgPRZrB0aj=ipzroc95xMLticzJfmxQMR56vdvOV-T8Xpk=tg@mail.gmail.com>
References: <CAMgPRZrB0aj=ipzroc95xMLticzJfmxQMR56vdvOV-T8Xpk=tg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Eoin O'Hehir <eoin.ohehir@clavisinsight.com> wrote:
> I'm setting up a weekly DB maintenance job for a 9.3 server.
>
> Part of this will be a VACUUM FULL.
That's something to seriously reconsider.
> Is there any point in adding the ANALYZE option to the command ?
That and a non-FULL VACUUM command after VACUUM FULL. Unlike what
you might expect based on the FULL option, a VACUUM FULL does not
do everything that a non-FULL VACUUM does, and actually drops any
existing visibility map and free space map -- potentially making
subsequent queries against the table slower until a normal VACUUM
(or autovacuum occurs). I strongly recommend that if you really do
need to use VACUUM FULL, you immediately follow it with VACUUM
ANALYZE.
You might also want to read this:
http://rhaas.blogspot.com/2014/03/vacuum-full-doesnt-mean-vacuum-but.html
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: kgrittn@ymail.com, eoin.ohehir@clavisinsight.com
Subject: Re: Does VACUUM FULL need ANALYZE ?
In-Reply-To: <76082180.506975.1435347618922.JavaMail.yahoo@mail.yahoo.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