Re: Autovacuum deadlock - bug or not?
От | Mikael Carneholm |
---|---|
Тема | Re: Autovacuum deadlock - bug or not? |
Дата | |
Msg-id | 7F10D26ECFA1FB458B89C5B4B0D72C2B0A01E2@sesrv12.wirelesscar.com обсуждение исходный текст |
Ответ на | Autovacuum deadlock - bug or not? ("Mikael Carneholm" <Mikael.Carneholm@WirelessCar.com>) |
Ответы |
Re: Autovacuum deadlock - bug or not?
|
Список | 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 по дате отправления: