public inbox for [email protected]
help / color / mirror / Atom feedFrom: Nathan Bossart <[email protected]>
To: Imseih (AWS), Sami <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: allow changing autovacuum_max_workers without restarting
Date: Thu, 11 Apr 2024 14:24:23 -0500
Message-ID: <20240411192423.GB2005410@nathanxps13> (raw)
In-Reply-To: <[email protected]>
References: <20240410212344.GA1824549@nathanxps13>
<[email protected]>
<20240411144240.GD1882158@nathanxps13>
<[email protected]>
On Thu, Apr 11, 2024 at 03:37:23PM +0000, Imseih (AWS), Sami wrote:
>> My concern with this approach is that other background workers could use up
>> all the slots and prevent autovacuum workers from starting
>
> That's a good point, the current settings do not guarantee that you
> get a worker for the purpose if none are available,
> i.e. max_parallel_workers_per_gather, you may have 2 workers planned
> and 0 launched.
>
>> unless of
>> course we reserve autovacuum_max_workers slots for _only_ autovacuum
>> workers. I'm not sure if we want to get these parameters tangled up like
>> this, though...
>
> This will be confusing to describe and we will be reserving autovac workers
> implicitly, rather than explicitly with a new GUC.
Yeah, that's probably a good reason to give autovacuum its own worker pool.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
view thread (6+ messages)
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]
Subject: Re: allow changing autovacuum_max_workers without restarting
In-Reply-To: <20240411192423.GB2005410@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