Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> What is state of this issue?
> http://archives.postgresql.org/pgsql-hackers/2011-09/msg00423.php

AFAICS we never identified the cause.  It was pretty clear that
something was failing to clean up shared-memory lock data structures,
but not what that something was.  The last productive suggestion was
to add process-exit-time logging of whether unreleased locks remain,
but if Dave ever did that, he didn't report back what he found.

Maybe you could add such logging on your machines.

			regards, tom lane

In response to

• lock AccessShareLock on object 0/1260/0 is already held at 2013-01-04 09:48:03 from Pavel Stehule

Responses

• Re: lock AccessShareLock on object 0/1260/0 is already held at 2013-01-04 17:10:15 from Pavel Stehule

pgsql-hackers by date

Next:	From: Alvaro Herrera	Date: 2013-01-04 17:08:35
	Subject: Re: PATCH: optimized DROP of multiple tables within a transaction
Previous:	From: Robert Haas	Date: 2013-01-04 16:42:07
	Subject: Re: PATCH: optimized DROP of multiple tables within a transaction