Cc: pgsql-admin@postgresql.org,"Sylvain CAILLET" <scaillet@alaloop.com>
Content-Type: text/plain; charset="utf-8"
Date: Thu, 20 Dec 2012 11:42:08 -0500
From: "Kevin Grittner" <kgrittn@mail.com>
Message-ID: <20121220164208.14700@gmx.com>
MIME-Version: 1.0
Subject: Re: Autovacuum issues with truncate and create index ...
To: "Baptiste LHOSTE" <blhoste@alaloop.com>
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Baptiste LHOSTE wrote:

> Here's the pg_stat_activity during the issue :
> [no processes waiting]

> Here's the pg_locks during the issue :
> [all locks granted]

Was the blocking you described occurring at the time you captured
this? It doesn't seem to be showing any problem.

> Is there a way to upgrade without having to dump all data and
> restore them after the upgrade ?

A minor release (where the version number doesn't change before the
second dot) never requires a dump and restore. There is sometimes a
need to do some cleanup work; for example, if a bug is fixed which
could corrupt a particular type of index, the release notes may
recommend rebuilding all indexes of that type to repair any damage
which may have occurred before the bug was fixed.

http://www.postgresql.org/support/versioning/

-Kevin


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin