From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: pplachta@gmail.com
Subject: BUG #17724: All autovacuum workers operate on 1 db at a time
Date: Fri, 16 Dec 2022 17:52:29 +0000
Message-ID: <17724-37442ada79498fbb@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 17724
Logged by: Peter Plachta
Email address: pplachta@gmail.com
PostgreSQL version: Unsupported/Unknown
Operating system: Windows (Azure)
Description:
Hi all
I have observed this on PG 9.6 and 10 and could not find a bug indicating it
was fixed.
Issue is that autovacuum workers appear bound to a certain DB, even if there
is more urgent (wraparound) work to do elsewhere.
In our case specifically we have multiple DBs, one has a large table that
for various reasons takes a long time (many hours) to vacuum. During this
time other autovacuum workers are idle while our other DBs which do frequent
insert/delete accumulate significant bloat which ends up affecting query
time.
Ideally the idle autovacuum workers would just proceed to the next DB.
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: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, pplachta@gmail.com
Subject: Re: BUG #17724: All autovacuum workers operate on 1 db at a time
In-Reply-To: <17724-37442ada79498fbb@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox