Date: Fri, 26 Jun 2015 19:40:18 +0000 (UTC)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
To: Eoin O'Hehir <eoin.ohehir@clavisinsight.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: <76082180.506975.1435347618922.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: 
 <CAMgPRZrB0aj=ipzroc95xMLticzJfmxQMR56vdvOV-T8Xpk=tg@mail.gmail.com>
References: 
 <CAMgPRZrB0aj=ipzroc95xMLticzJfmxQMR56vdvOV-T8Xpk=tg@mail.gmail.com>
Subject: Re: Does VACUUM FULL need ANALYZE ?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Length: 934
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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