Re: Autovacuum deadlock - bug or not? - Mailing list pgsql-bugs

From Mikael Carneholm
Subject Re: Autovacuum deadlock - bug or not?
Date
Msg-id 7F10D26ECFA1FB458B89C5B4B0D72C2B0A01E2@sesrv12.wirelesscar.com
Whole thread Raw
In response to Autovacuum deadlock - bug or not?  ("Mikael Carneholm" <Mikael.Carneholm@WirelessCar.com>)
Responses Re: Autovacuum deadlock - bug or not?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Unfortunately, relfilenodes 68950 and 68122 don't exist anymore, could be t=
hat they were temporary copies of tables or indexes. I know that process 15=
865 was the autovacuum pid, I looked that up when it happened (pg was resta=
rted with autovacuum=3Doff 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@sss.pgh.pa.us]
Sent: den 17 november 2005 16:04
To: Mikael Carneholm
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Autovacuum deadlock - bug or not?=20


"Mikael Carneholm" <Mikael.Carneholm@WirelessCar.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

pgsql-bugs by date:

Previous
From: Matt
Date:
Subject: Huge query stalls at PARSE/BIND stage (1)
Next
From: "Mikael Carneholm"
Date:
Subject: Re: Autovacuum deadlock - bug or not?