pg_autovacuum taking locks on multiple tables at the same time - Mailing list pgsql-general

From Hari Bhaskaran
Subject pg_autovacuum taking locks on multiple tables at the same time
Date
Msg-id 452AB9A7.9060300@gmail.com
Whole thread Raw
Responses Re: pg_autovacuum taking locks on multiple tables at the same time  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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)


pgsql-general by date:

Previous
From: Ivan Sergio Borgonovo
Date:
Subject: Re: Determining caller of a function (due to a cascaded
Next
From: "Merlin Moncure"
Date:
Subject: Re: plpgsql handling a set of values