Date: Wed, 3 Sep 2025 16:36:47 -0500
From: Nathan Bossart <nathandbossart@gmail.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: GetNamedLWLockTranche crashes on Windows in normal backend
Message-ID: <aLi075cWNyXQw-6G@nathan>
References: 
 <CAA5RZ0v1_15QPg5Sqd2Qz5rh_qcsyCeHHmRDY89xVHcy2yt5BQ@mail.gmail.com>
 <aKyTa-iOdAfKynI1@nathan>
 <CAA5RZ0u4BDp4ENjOyZ7NADz+jdQY-=PZFQNsf0jBt1Va4QzoAA@mail.gmail.com>
 <aKyr_rVOtlolDcy-@nathan>
 <CAA5RZ0un+WRqsM35JUE97LOdrjGbE1VZpL0h0kaQn-_y5j8U0A@mail.gmail.com>
 <aKyzQuljgqo7-YIs@nathan>
 <CAA5RZ0tuKYaaS3ohjqXzxgk7xExz1VdP4Xyay9YxemJWr4vAfg@mail.gmail.com>
 <CAA5RZ0tUApqNpYbRq9dtWZZyWd8FhJxxjOLbU8yso=opJMuHtQ@mail.gmail.com>
 <aKzYgi0TbmcG-Y9l@nathan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <aKzYgi0TbmcG-Y9l@nathan>
Archived-At: <https://www.postgresql.org/message-id/aLi075cWNyXQw-6G%40nathan>
Precedence: bulk

Well, commit 38b602b certainly doesn't do us any favors here since it
removed NamedLWLockTrancheArray.  Given the lack of reports from the field,
I suspect the best path forward is to add an ERROR for unsafe accesses and
to fix the documentation, as discussed upthread.

-- 
nathan