Re: Autovacuum issues with truncate and create index ...

From: "Kevin Grittner" <kgrittn(at)mail(dot)com>
To: "Baptiste LHOSTE" <blhoste(at)alaloop(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org,"Sylvain CAILLET" <scaillet(at)alaloop(dot)com>
Subject: Re: Autovacuum issues with truncate and create index ...
Date: 2012-12-20 16:42:08
Message-ID: 20121220164208.14700@gmx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Baptiste LHOSTE 2012-12-20 17:08:43 Re: Autovacuum issues with truncate and create index ...
Previous Message Baptiste LHOSTE 2012-12-20 16:11:09 Re: Autovacuum issues with truncate and create index ...