Re: Autovacuum deadlock - bug or not?

Unfortunately, relfilenodes 68950 and 68122 don't exist anymore, could be that they were temporary copies of tables or indexes. I know that process 15865 was the autovacuum pid, I looked that up when it happened (pg was restarted with autovacuum=off afterwards, so that process is also gone)

Could it be that the deadlock was caused by autovacuum trying to vacuum one of the temp copies?

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: den 17 november 2005 16:04
To: Mikael Carneholm
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] Autovacuum deadlock - bug or not?

"Mikael Carneholm" <Mikael(dot)Carneholm(at)WirelessCar(dot)com> writes:
> variant: CLUSTER indexname ON tablename

Hmph. Looking at the code, that should always lock the table first,
so I don't see where the problem is. Would you look up the numbers
for us --- exactly which relations were involved in the deadlock,
and (if you can tell) which process was which?

Also, what PG version is this exactly?

regards, tom lane