Re: "ERROR: latch already owned" on gharial - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: "ERROR: latch already owned" on gharial
Date
Msg-id CA+hUKG+-MZjLJQ7YAbGnG3z-ObWtxQUAdRsDTbvtB-2Vy9G+HA@mail.gmail.com
Whole thread Raw
In response to Re: "ERROR: latch already owned" on gharial  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "ERROR: latch already owned" on gharial
List pgsql-hackers
On Thu, May 26, 2022 at 2:25 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Noah Misch <noah@leadboat.com> writes:
> > +1, this is at least the third non-obvious miscompilation from gharial.
>
> Is there any evidence that this is a compiler-sourced problem?
> Maybe it is, but it's sure not obvious to me (he says, eyeing his
> buildfarm animals with even older gcc versions).

Sorry for the ambiguity -- I have no evidence of miscompilation.  My
"just BTW" paragraph was a reaction to the memory of the last couple
of times Noah and I wasted hours chasing red herrings on this system,
which is pretty demotivating when looking into an unexplained failure.

On a more practical note, I don't have access to the BF database right
now.  Would you mind checking if "latch already owned" has occurred on
any other animals?



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [RFC] building postgres with meson
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample