Re: finding the other statement causing a sharelock

From: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: finding the other statement causing a sharelock
Date: 2010-11-08 21:53:06
Message-ID: 20101108225306.1173bc25@dawn.webthatworks.it
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 8 Nov 2010 14:22:16 -0700
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jason Long 2010-11-08 21:53:26 Re: Full Vacuum/Reindex vs autovacuum
Previous Message John R Pierce 2010-11-08 21:28:27 Re: Full Vacuum/Reindex vs autovacuum