pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #17724: All autovacuum workers operate on 1 db at a time
2+ messages / 2 participants
[nested] [flat]
* BUG #17724: All autovacuum workers operate on 1 db at a time
@ 2022-12-16 17:52 PG Bug reporting form <noreply@postgresql.org>
2022-12-16 21:26 ` Re: BUG #17724: All autovacuum workers operate on 1 db at a time David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2022-12-16 17:52 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: pplachta@gmail.com
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #17724: All autovacuum workers operate on 1 db at a time
2022-12-16 17:52 BUG #17724: All autovacuum workers operate on 1 db at a time PG Bug reporting form <noreply@postgresql.org>
@ 2022-12-16 21:26 ` David G. Johnston <david.g.johnston@gmail.com>
0 siblings, 0 replies; 2+ messages in thread
From: David G. Johnston @ 2022-12-16 21:26 UTC (permalink / raw)
To: pplachta@gmail.com; pgsql-bugs@lists.postgresql.org
On Fri, Dec 16, 2022 at 2:13 PM PG Bug reporting form <
noreply@postgresql.org> wrote:
> 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.
>
>
This doesn't qualify as a bug report. If you need assistance diagnosing
issues on your system you should use the -general mailing list, or maybe
visit a forum like Slack or Discord where once you find someone willing to
help, communications tend to be much more interactive/timely in nature.
I would suggest you upgrade to a supported release in any case.
As for diagnostics, the system is capable of producing logs, and also has
views, regarding the autovacuum daemon. You should share this raw data
instead of simply giving your interpretation of what you saw.
Sharing the relevant configuration setting values for the autovacuum daemon
is also recommended.
David J.
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-12-16 21:26 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-12-16 17:52 BUG #17724: All autovacuum workers operate on 1 db at a time PG Bug reporting form <noreply@postgresql.org>
2022-12-16 21:26 ` David G. Johnston <david.g.johnston@gmail.com>
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