From: | "Mikael Carneholm" <Mikael(dot)Carneholm(at)WirelessCar(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Autovacuum deadlock - bug or not? |
Date: | 2005-11-17 16:28:22 |
Message-ID: | 7F10D26ECFA1FB458B89C5B4B0D72C2B088216@sesrv12.wirelesscar.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
oops, you're right.
dfol=> select pgc.oid, pgc.relname from pg_class pgc where pgc.oid in (68950, 68122);
oid | relname
-------+--------------------------
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 database 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_person_information__id on vehicle_unit_data_200407 that caused the deadlock.
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: den 17 november 2005 16:53
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:
> Unfortunately, relfilenodes 68950 and 68122 don't exist anymore,
You should be looking at pg_class.oid, not relfilenode.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-17 16:41:57 | Re: Autovacuum deadlock - bug or not? |
Previous Message | Tom Lane | 2005-11-17 15:53:16 | Re: Autovacuum deadlock - bug or not? |