From: Kevin Grittner <kgrittn@mail.com>
To: Baptiste LHOSTE <blhoste@alaloop.com>
To: pgsql-admin@postgresql.org
Subject: Re: Autovacuum issues with truncate and create index ...
Date: Thu, 20 Dec 2012 10:04:30 -0500
Message-ID: <20121220150431.14740@gmx.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Baptiste LHOSTE wrote:
> - finally we delete old data of the second kind of tables
> Then the autovacuum process starts to work on the second kind of
> tables, but our process blocks into step 3 (truncate) or step 5
> (create index).
>
> As soon as I reset the autovacuum thresholds for the second kind
> of tables, our process run again perfectly.
>
> Can our process could create deadlock with the autovacuum
> process ?
Would it be possible for you to create such a situation and capture
the contents of pg_stat_activity and pg_locks while it is going on?
What messages related to autovacuum or deadlocks do you see in the
server log while this is going on?
> PostgreSQL 8.4.11
Would it be possible to update your 8.4 installation to the latest
bug fix (currently 8.4.15) to rule out the influence of any bugs
which have already been fixed?
-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
Subject: Re: Autovacuum issues with truncate and create index ...
In-Reply-To: <20121220150431.14740@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