| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Junwang Zhao <zhjwpku(at)gmail(dot)com> |
| Cc: | Nikita Malakhov <hukutoc(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Introduce some randomness to autovacuum |
| Date: | 2025-04-30 17:06:35 |
| Message-ID: | CAKAnmmJ5yb_gMYyDW1B_TK_RP3j3D1nJu3EzS1JvT3qDx6FCuA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 30, 2025 at 10:07 AM Junwang Zhao <zhjwpku(at)gmail(dot)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
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-04-30 17:15:46 | Re: pgsql: Add function to log the memory contexts of specified backend pro |
| Previous Message | Sami Imseih | 2025-04-30 16:38:08 | Re: Introduce some randomness to autovacuum |