2013/1/4 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> What is state of this issue?
> 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.
probably I am able to find statement, that was canceled as last
"success" statement from our application logs. And probably it will be
LOCK ... or CREATE TABLE AS SELECT
Recheck on session end can help us to drop this leaked locks, but I
don't understand how it can help with finding with finding the cause?
> Maybe you could add such logging on your machines.
> regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2013-01-04 17:10:16|
|Subject: Re: enhanced error fields|
|Previous:||From: Alvaro Herrera||Date: 2013-01-04 17:08:35|
|Subject: Re: PATCH: optimized DROP of multiple tables within a