Re: Disabling vacuum truncate for autovacuum
Laurenz Albe <laurenz.albe@cybertec.at>
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Nathan Bossart <nathandbossart@gmail.com>, Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Gurjeet Singh <gurjeet@singh.im>, Robert Haas <robertmhaas@gmail.com>,
Postgres Hackers <pgsql-hackers@postgresql.org>, Will Storey
<will@summercat.com>
Date: 2025-03-14T21:01:09Z
Lists: pgsql-hackers, pgsql-general
On Fri, 2025-03-14 at 10:42 -0500, Nathan Bossart wrote: > One other difference in my version of the patch [0] is to call this GUC > vacuum_truncate and have it apply to both autovacuum and VACUUM. I agree that that is the way to go. It makes no sense to restrict the feature to autovacuum. Yours, Laurenz Albe
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Expand comment for isset_offset.
- 7d559c8580f7 18.0 landed
-
Add vacuum_truncate configuration parameter.
- 0164a0f9ee12 18.0 landed