Re: Autovacuum issues with truncate and create index ... - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: Autovacuum issues with truncate and create index ...
Date
Msg-id 20121220164208.14700@gmx.com
Whole thread Raw
In response to Autovacuum issues with truncate and create index ...  (Baptiste LHOSTE <blhoste@alaloop.com>)
Responses Re: Autovacuum issues with truncate and create index ...  (Baptiste LHOSTE <blhoste@alaloop.com>)
List pgsql-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


pgsql-admin by date:

Previous
From: Baptiste LHOSTE
Date:
Subject: Re: Autovacuum issues with truncate and create index ...
Next
From: Baptiste LHOSTE
Date:
Subject: Re: Autovacuum issues with truncate and create index ...