pg_autovacuum taking locks on multiple tables at the same time

From: Hari Bhaskaran <hbhaskaran(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: pg_autovacuum taking locks on multiple tables at the same time
Date: 2006-10-09 21:05:43
Message-ID: 452AB9A7.9060300@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

This is causing a headache for us, if that is indeed true.

So we have code that goes like

begin;
lock table t1;
lock table t2;
...
...

Of course within our own code, we do make sure things are always locked
in the same order (so we wouldn't create deadlocks). We do, however, end
up in deadlocks with pg_autovacuum which seem to take lock in different
order.

Why does pg_autovacuum need locks on more than one table at a time?
(there tables in question are NOT related to each other via foriegn keys)

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2006-10-09 21:11:29 Re: plpgsql handling a set of values
Previous Message Ivan Sergio Borgonovo 2006-10-09 20:46:50 Re: Determining caller of a function (due to a cascaded