Re: autovacuum and deadlocks - Mailing list pgsql-general

From Scott Marlowe
Subject Re: autovacuum and deadlocks
Date
Msg-id CAOR=d=3MSTyab5VK3hrZOw+3MMm5fX+5_AehmQDKioUeSjSsXw@mail.gmail.com
Whole thread Raw
In response to autovacuum and deadlocks  (Gregg Jaskiewicz <gryzman@gmail.com>)
List pgsql-general
On Sat, Feb 18, 2012 at 8:59 AM, Gregg Jaskiewicz <gryzman@gmail.com> wrote:
> What is a likelihood of a deadlock occurring, caused (or helped by)
> auto vacuum.
> This is on 8.3.
>
> The table with deadlocks was quite busy with updates, etc.

The only locking issues (not deadlocks) I've ever had with autovacuum
were priority inversion issues with slony, where a slony execute
script was stuck behind an autovacuum, and something else was then
stuck behind the slony execute script.

I'm afraid we'll need more info to determine what was happening.  It's
a good idea to make a snapshot of what's in pg_stat_activity and
pg_locks when these things happen so you have something to look at
after the fact.

pgsql-general by date:

Previous
From: Gregg Jaskiewicz
Date:
Subject: autovacuum and deadlocks
Next
From: Susanne Ebrecht
Date:
Subject: Re: MySQL search query is not executing in Postgres DB