Re: Introduce some randomness to autovacuum - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Introduce some randomness to autovacuum
Date
Msg-id CAKAnmmJ5yb_gMYyDW1B_TK_RP3j3D1nJu3EzS1JvT3qDx6FCuA@mail.gmail.com
Whole thread Raw
In response to Re: Introduce some randomness to autovacuum  (Junwang Zhao <zhjwpku@gmail.com>)
Responses Re: Introduce some randomness to autovacuum
List pgsql-hackers
On Wed, Apr 30, 2025 at 10:07 AM Junwang Zhao <zhjwpku@gmail.com> wrote:
I ended up with adding a guc configuration that may support different vacuum
strategies.

+1 to this: it's a good solution to a tricky problem. I would be a -1 if this were not a GUC.

Yes, it is masking the problem, but maybe a better way to think about it is that it is delaying the performance impact, allowing more time for a manual intervention of the problematic table(s).

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Introduce some randomness to autovacuum
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Add function to log the memory contexts of specified backend pro