Re: Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep
Date
Msg-id YQH7uLYwTvNC2xyL@paquier.xyz
Whole thread Raw
In response to Re: Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: Use WaitLatch for {pre, post}_auth_delay instead of pg_usleep  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
List pgsql-hackers
On Wed, Jul 28, 2021 at 08:28:12PM +0000, Bossart, Nathan wrote:
> On 7/28/21, 11:32 AM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>> I follow the idea of using WaitLatch to ensure that the delays are
>> interruptible by postmaster signals, but even that isn't worth a
>> lot given the expected use of these things.  I don't see a need to
>> expend any extra effort on wait-reporting.
>
> +1.  The proposed patch doesn't make the delay visibility any worse
> than what's already there.

Agreed to just drop the patch (my opinion about this patch is
unchanged).  Not to mention that wait events are not available at SQL
level at this stage yet.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Out-of-memory error reports in libpq
Next
From: Michael Paquier
Date:
Subject: Re: Emit namespace in post-copy output