Re: finding the other statement causing a sharelock

On Mon, 8 Nov 2010 14:22:16 -0700
Scott Marlowe <scott.marlowe@gmail.com> wrote:

> Don't know how much it helps here, but this page:
> http://wiki.postgresql.org/wiki/Lock_Monitoring
> is priceless when you're having issues midday with a lock that
> won't go away.

I was thinking to reinvent the wheel and write something similar.

But I was already thinking how am I supposed to "intercept" a lock
that is caused by a long transaction that I know and a process
happening at some unknown time?

I've some strong suspect... and I'd like to exit earlier from a
function if a process is running but I'm not really sure how to add a
semaphore...

--
Ivan Sergio Borgonovo
http://www.webthatworks.it