Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #6065: FATAL: lock 0 not held - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6065: FATAL: lock 0 not held
Date
Msg-id 16155.1308320886@sss.pgh.pa.us
Whole thread Raw
In response to BUG #6065: FATAL: lock 0 not held  ("Ben" <bwtest24@yahoo.com>)
List pgsql-bugs
Tree view 
"Ben" <bwtest24@yahoo.com> writes:
> Operating system:   üLinux version 2.6.21-uc0 on ARM processor
> (NXP-LPC2478)
> Description:        FATAL: lock 0 not held
> Details:

> while initialising with initdb, after creating and filling new WAL file.
> We see LWLockAcquire(11) followed by LWLockRelease(0) and then a FATAL:
> lock 0 is not held.

Compiler bug?  It's pretty hard to credit that you've found some new
code path through bootstrap where the wrong lock number gets frobbed.

We do have at least one buildfarm member running on ARM, so that
architecture does get tested regularly, which eliminates various
other theories about PG portability problems.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #6066: [PATCH] Mark more strings as c-format
Next
From: Tom Lane
Date:
Subject: Re: Ident authentication fails due to bind error on server (8.4.8)