public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Thomas Munro <[email protected]>
Cc: Noah Misch <[email protected]>
Cc: Andres Freund <[email protected]>
Cc: CM Team <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: "ERROR: latch already owned" on gharial
Date: Wed, 25 May 2022 22:35:06 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+hUKG+-MZjLJQ7YAbGnG3z-ObWtxQUAdRsDTbvtB-2Vy9G+HA@mail.gmail.com>
References: <CA+hUKGJ_0RGcr7oUNzcHdn7zHqHSB_wLSd3JyS2YC_DYB+-V=g@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<CA+hUKG+-MZjLJQ7YAbGnG3z-ObWtxQUAdRsDTbvtB-2Vy9G+HA@mail.gmail.com>
Thomas Munro <[email protected]> writes:
> 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.
I can't deny that those HPUX animals have produced more than their
fair share of problems.
> 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?
Looking back 6 months, these are the only occurrences of that string
in failed tests:
sysname | branch | snapshot | stage | l
---------+--------+---------------------+----------------+-------------------------------------------------------------------
gharial | HEAD | 2022-04-28 23:37:51 | Check | 2022-04-28 18:36:26.981 MDT [22642:1] ERROR: latch already owned
gharial | HEAD | 2022-05-06 11:33:11 | IsolationCheck | 2022-05-06 10:10:52.727 MDT [7366:1] ERROR: latch already owned
gharial | HEAD | 2022-05-24 06:31:31 | IsolationCheck | 2022-05-24 02:44:51.850 MDT [13089:1] ERROR: latch already owned
(3 rows)
regards, tom lane
view thread (20+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: "ERROR: latch already owned" on gharial
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox