pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedLock Error
4+ messages / 3 participants
[nested] [flat]
* Lock Error
@ 2017-01-11 00:17 ProPAAS DBA <dba@propaas.com>
2017-01-11 02:26 ` Re: Lock Error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: ProPAAS DBA @ 2017-01-11 00:17 UTC (permalink / raw)
To: pgsql-admin
Hi all;
Anyone know what the cause of this error might be?
ERROR: lock main [some number] is not held
for example:
ERROR: lock main 74764 is not held
Thanks in advance...
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Lock Error
2017-01-11 00:17 Lock Error ProPAAS DBA <dba@propaas.com>
@ 2017-01-11 02:26 ` Tom Lane <tgl@sss.pgh.pa.us>
2017-01-11 04:50 ` Re: Lock Error ProPAAS DBA <dba@propaas.com>
0 siblings, 1 reply; 4+ messages in thread
From: Tom Lane @ 2017-01-11 02:26 UTC (permalink / raw)
To: ProPAAS DBA <dba@propaas.com>; +Cc: pgsql-admin
ProPAAS DBA <dba@propaas.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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Lock Error
2017-01-11 00:17 Lock Error ProPAAS DBA <dba@propaas.com>
2017-01-11 02:26 ` Re: Lock Error Tom Lane <tgl@sss.pgh.pa.us>
@ 2017-01-11 04:50 ` ProPAAS DBA <dba@propaas.com>
2017-01-16 08:04 ` Re: Lock Error Jan Harasym <jan.harasym@massive.se>
0 siblings, 1 reply; 4+ messages in thread
From: ProPAAS DBA @ 2017-01-11 04:50 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
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@propaas.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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Lock Error
2017-01-11 00:17 Lock Error ProPAAS DBA <dba@propaas.com>
2017-01-11 02:26 ` Re: Lock Error Tom Lane <tgl@sss.pgh.pa.us>
2017-01-11 04:50 ` Re: Lock Error ProPAAS DBA <dba@propaas.com>
@ 2017-01-16 08:04 ` Jan Harasym <jan.harasym@massive.se>
0 siblings, 0 replies; 4+ messages in thread
From: Jan Harasym @ 2017-01-16 08:04 UTC (permalink / raw)
To: 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@propaas.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
>
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2017-01-16 08:04 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-01-11 00:17 Lock Error ProPAAS DBA <dba@propaas.com>
2017-01-11 02:26 ` Tom Lane <tgl@sss.pgh.pa.us>
2017-01-11 04:50 ` ProPAAS DBA <dba@propaas.com>
2017-01-16 08:04 ` Jan Harasym <jan.harasym@massive.se>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox