Re: another autovacuum scheduling thread
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Sami Imseih <samimseih@gmail.com>,
Nathan Bossart <nathandbossart@gmail.com>, Robert Treat <rob@xzilla.net>, Jeremy Schneider <schneider@ardentperf.com>,
pgsql-hackers@postgresql.org
Date: 2025-11-20T21:16:23Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Add rudimentary table prioritization to autovacuum.
- d7965d65fc5b 19 (unreleased) landed
-
Trigger more frequent autovacuums with relallfrozen
- 06eae9e6218a 18.0 cited
-
Harden nbtree page deletion.
- c34787f91058 14.0 cited
-
Check for interrupts inside the nbtree page deletion code.
- 3a01f68e35a3 12.0 cited
On Thu, Nov 20, 2025 at 3:58 PM David Rowley <dgrowleyml@gmail.com> wrote: > before we need to make a decision. My vote is to use as much of that > time as possible rather than using it to allow people to dream up > hypothetical problems that might or might not exist. That seems a little harsh. I think the only hypothesis necessary for my concern to be valid is the hypothesis that whatever algorithm we've selected may not always work well. I admit that I could be wrong in thinking so; there are plenty of heuristics in PostgreSQL that are so effective that nobody ever cares about tuning them. But there's enough problems with autovacuum that I don't think it's a particularly adventurous hypothesis, either. That said, I accept your point that even if we were to agree that something ought to made tunable here, we would still have the problem of deciding exactly what GUCs or reloptions to add, and that might be hard to figure out without more information. Unfortunately, I have a feeling that unless you or someone here is planning to make a determined testing effort over the coming months, we're more likely to get feedback after final release than during development or even beta. But I do also understand that you don't want us to be paralyzed and never move forward. -- Robert Haas EDB: http://www.enterprisedb.com