From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
cc: Thomas Munro <thomas.munro@gmail.com>, Noah Misch <noah@leadboat.com>,
        Andres Freund <andres@anarazel.de>, CM Team <cm@enterprisedb.com>,
        pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: "ERROR: latch already owned" on gharial
In-reply-to: 
 <CA+TgmoYGrNN2gpDQXiEZ3GmNso8n4h5WecR9vfGnDrxtRrBASA@mail.gmail.com>
References: 
 <CA+hUKGJ_0RGcr7oUNzcHdn7zHqHSB_wLSd3JyS2YC_DYB+-V=g@mail.gmail.com>
 <20220525012439.pkrfb7zh276jdmyq@alap3.anarazel.de>
 <20220525064658.GA3123194@rfd.leadboat.com>
 <1921928.1653488733@sss.pgh.pa.us>
 <CA+hUKG+-MZjLJQ7YAbGnG3z-ObWtxQUAdRsDTbvtB-2Vy9G+HA@mail.gmail.com>
 <2085124.1653532506@sss.pgh.pa.us>
 <CA+hUKG+YuSJzKtJkGaXnD+JpZ0MFB5RBdhHK9_VOgzOVSSNyWA@mail.gmail.com>
 <CA+Tgmob=gwJcMWE3oVg=TV+CnJzN+kxwk5KzYyTyC=OD4mLUoA@mail.gmail.com>
 <2643515.1653661311@sss.pgh.pa.us>
 <CA+TgmoYGrNN2gpDQXiEZ3GmNso8n4h5WecR9vfGnDrxtRrBASA@mail.gmail.com>
Comments: In-reply-to Robert Haas <robertmhaas@gmail.com>
	message dated "Fri, 27 May 2022 15:44:44 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2728961.1653682304.1@sss.pgh.pa.us>
Date: Fri, 27 May 2022 16:11:44 -0400
Message-ID: <2728962.1653682304@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2728962.1653682304%40sss.pgh.pa.us>
Precedence: bulk

Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, May 27, 2022 at 10:21 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> What I'd suggest is to promote that failure to elog(PANIC), which
>> would at least give us the PID and if we're lucky a stack trace.

> That proposed change is fine with me.

> As to the question of whether it's a real bug, nobody can prove
> anything unless we actually run it down.

Agreed, and I'll even grant your point that if it is an HPUX-specific
or IA64-specific bug, it is not worth spending huge amounts of time
to isolate.  The problem is that we don't know that.  What we do know
so far is that if it can occur elsewhere, it's rare --- so we'd better
be prepared to glean as much info as possible if we do get such a
failure.  Hence my thought of s/ERROR/PANIC/.  And I'd be in favor of
any other low-effort change we can make to instrument the case better.

			regards, tom lane