Re: lock AccessShareLock on object 0/1260/0 is already held - Mailing list pgsql-hackers

From Tom Lane
Subject Re: lock AccessShareLock on object 0/1260/0 is already held
Date
Msg-id 20766.1357318482@sss.pgh.pa.us
Whole thread Raw
In response to lock AccessShareLock on object 0/1260/0 is already held  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: lock AccessShareLock on object 0/1260/0 is already held
List pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PATCH: optimized DROP of multiple tables within a transaction
Next
From: Alvaro Herrera
Date:
Subject: Re: PATCH: optimized DROP of multiple tables within a transaction