Hello, the problem just resurfaced and the Wiki page dows not really help very much. When i look into the pg_stat_activity, i only see that the connections all state "<IDLE> in transaction". Is there any way to find out what the transaction is doing exactly to be able to debug the Problem? Best regards Manuel Tuesday, June 7, 2011, 5:50:13 PM, you wrote: T> Hi Scott, SM>> Snip. Those are ALL either AccessShareLock (which is very low level SM>> and non-blocking) or virtual tx locks, which again don't block SM>> anything but their own transaction. Nothing there screams "locks!" SM>> for a better view of locks and how they're blocking things you can use SM>> the queries from here: http://wiki.postgresql.org/wiki/Lock_Monitoring T> Thank you, I will try that. I am currently using Hibernate 3.2 as a T> Database-Layer but with an older JDBC for 8.2, i will try updating T> these components to more recent versions. T> If the problem arises again i will hopefully be able to better T> analyze, where the locking in my application occurs. It is in fact a T> multi-threaded environment. T> Best regards T> Manuel -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
