From: Kevin Grittner <kgrittn@mail.com>
To: Baptiste LHOSTE <blhoste@alaloop.com>
Cc: pgsql-admin@postgresql.org,"Sylvain CAILLET" <scaillet@alaloop.com>
Subject: Re: Autovacuum issues with truncate and create index ...
Date: Thu, 20 Dec 2012 11:42:08 -0500
Message-ID: <20121220164208.14700@gmx.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
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@mail.com, blhoste@alaloop.com, scaillet@alaloop.com
Subject: Re: Autovacuum issues with truncate and create index ...
In-Reply-To: <20121220164208.14700@gmx.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