| From: | Jan Harasym <jan(dot)harasym(at)massive(dot)se> |
|---|---|
| To: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Lock Error |
| Date: | 2017-01-16 08:04:14 |
| Message-ID: | 19ae3169-5a61-45d1-94e6-a0a75e007953@massive.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
It would also be great to know the version of PG, since it could have
been a long fixed bug.
Thanks.
On 11/01/2017 05:50, ProPAAS DBA wrote:
> I'll check with the client and see if we can re-create it, they claim
> this error is happening daily. Would a log file help to start with?
>
>
>
> On 01/10/2017 07:26 PM, Tom Lane wrote:
>> ProPAAS DBA <dba(at)propaas(dot)com> writes:
>>> Anyone know what the cause of this error might be?
>>> ERROR: lock main [some number] is not held
>> That would be a bug. If you can reproduce it, we'd like to see how.
>>
>> regards, tom lane
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ravi Tammineni | 2017-01-17 19:31:31 | Queries are taking way longer in 9.6 than 9.5 |
| Previous Message | Tom Lane | 2017-01-11 22:46:52 | Re: vacuum toast loop? |