On Fri, Nov 18, 2005 at 05:00:06PM +0100, Csaba Nagy wrote: > This current situation is different, the machine was almost idle, and > there was 1 UPDATE on a table running, a lot of inserts on the same > table waiting for a lock held by the transaction of the UPDATE, and a > VACUUM (started by autovacuum) running on the same table. There was no > dead-lock detected by the system, and I guess it should have detected it > if it was one, cause this whole thing was running for more than 3 hours > according to pg_stat_activity, and I set the deadlock timeout to 2 > seconds. So what is the UPDATE doing? What is the query (see pg_stat_activity) doing? Is it updating a lot of rows? If the query does run for a long time holding any kind of lock, you're going to get strange effects like this. Have a nice day, -- Martijn van Oosterhout <kleptog@xxxxxxxxx> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Attachment:
pgp3IGD53rLho.pgp
Description: PGP signature
