Hello
2013/1/4 Pavel Stehule :
> 2013/1/4 Tom Lane :
>> Pavel Stehule 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-me
2013/1/4 Tom Lane :
> Pavel Stehule 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 wha
Pavel Stehule 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
Hello
What is state of this issue?
http://archives.postgresql.org/pgsql-hackers/2011-09/msg00423.php
We detect this issue in our servers - we use 9.1.6 on Linux
locktype | database | relation | page | tuple | virtualxid |
transactionid | classid | objid | objsubid | virtualtransaction | pid
|
