Re: New GUC autovacuum_max_threshold ?
Frédéric Yhuel <frederic.yhuel@dalibo.com>
From: Frédéric Yhuel <frederic.yhuel@dalibo.com>
To: Nathan Bossart <nathandbossart@gmail.com>,
Robert Haas <robertmhaas@gmail.com>
Cc: "Imseih (AWS), Sami" <simseih@amazon.com>,
David Rowley <dgrowleyml@gmail.com>, Joe Conway <mail@joeconway.com>,
Michael Banck <mbanck@gmx.net>, Laurenz Albe <laurenz.albe@cybertec.at>,
Melanie Plageman <melanieplageman@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-06-18T10:36:42Z
Lists: pgsql-hackers
Le 18/06/2024 à 05:06, Nathan Bossart a écrit : > I didn't see a commitfest entry for this, so I created one to make sure we > don't lose track of this: > > https://commitfest.postgresql.org/48/5046/ > OK thanks! By the way, I wonder if there were any off-list discussions after Robert's conference at PGConf.dev (and I'm waiting for the video of the conf).
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Introduce autovacuum_vacuum_max_threshold.
- 306dc520b9df 18.0 landed
-
Consolidate docs for vacuum-related GUCs in new subsection
- ca9c6a5680d7 18.0 cited