public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nathan Bossart <[email protected]>
To: Andres Freund <[email protected]>
Cc: David Geier <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Fix assertion in autovacuum worker
Date: Wed, 29 Nov 2023 11:52:01 -0600
Message-ID: <20231129175201.GA902323@nathanxps13> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<20231128220516.GA475168@nathanxps13>
<[email protected]>
<20231129024247.GA479372@nathanxps13>
<[email protected]>
On Tue, Nov 28, 2023 at 06:48:59PM -0800, Andres Freund wrote:
> On 2023-11-28 20:42:47 -0600, Nathan Bossart wrote:
>> Right. Perhaps we could add a LWLockReleaseAll() to
>> pgstat_shutdown_hook() instead of the autovacuum code, but I'm afraid that
>> is still just a hack.
>
> Yea, we'd need that in just about all before_shmem_exit() callbacks. I could
> see an argument for doing it in proc_exit_prepare(). While that'd be a fairly
> gross layering violation, we already do reset a number a bunch of stuff in
> there:
Gross layering violations aside, that at least seems more future-proof
against other sigsetjmp() blocks that proc_exit() without doing any
preliminary cleanup.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
view thread (7+ 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]
Subject: Re: Fix assertion in autovacuum worker
In-Reply-To: <20231129175201.GA902323@nathanxps13>
* 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