oops, you're right.
dfol=3D> select pgc.oid, pgc.relname from pg_class pgc where pgc.oid in (68=
950, 68122);
oid | relname=20=20=20=20=20=20=20=20=20=20
-------+--------------------------
68950 | vehicle_unit_data_200407
68122 | vehicle_unit_data_200301
NOTICE: Clustering idx_vehicle_unit_data_200407_person_information__id on =
vehicle_unit_data_200407
ERROR: deadlock detected
DETAIL: Process 29022 waits for AccessExclusiveLock on relation 68950 of d=
atabase 16390; blocked by process 15865.
Process 15865 waits for AccessShareLock on relation 68122 of database 16390=
; blocked by process 29022.
So it seems that it was the clustering of idx_vehicle_unit_data_200407_pers=
on_information__id on vehicle_unit_data_200407 that caused the deadlock.
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: den 17 november 2005 16:53
To: Mikael Carneholm
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] Autovacuum deadlock - bug or not?=20
"Mikael Carneholm" <Mikael.Carneholm@WirelessCar.com> writes:
> Unfortunately, relfilenodes 68950 and 68122 don't exist anymore,
You should be looking at pg_class.oid, not relfilenode.
regards, tom lane
