From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, CM Team <cm(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "ERROR: latch already owned" on gharial |
Date: | 2022-05-26 01:50:00 |
Message-ID: | CA+hUKG+-MZjLJQ7YAbGnG3z-ObWtxQUAdRsDTbvtB-2Vy9G+HA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, May 26, 2022 at 2:25 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Noah Misch <noah(at)leadboat(dot)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?
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2022-05-26 02:10:18 | Re: fix stats_fetch_consistency value in postgresql.conf.sample |
Previous Message | Tom Lane | 2022-05-26 01:38:33 | Re: [RFC] building postgres with meson |