Re: Disabling vacuum truncate for autovacuum
David G. Johnston <david.g.johnston@gmail.com>
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Robert Treat <rob@xzilla.net>, Laurenz Albe <laurenz.albe@cybertec.at>, Gurjeet Singh <gurjeet@singh.im>, Andres Freund <andres@anarazel.de>, Will Storey <will@summercat.com>, Robert Haas <robertmhaas@gmail.com>,
Postgres Hackers <pgsql-hackers@postgresql.org>
Date: 2025-03-21T15:54:55Z
Lists: pgsql-hackers, pgsql-general
On Thu, Mar 20, 2025 at 11:13 AM Nathan Bossart <nathandbossart@gmail.com> wrote: > > How does something like this look for the comment? > > /* > * isset_offset is an optional offset of a field in the result > struct > * that stores whether the value is explicitly set for the > relation or > * has just picked up the default value. In most cases, this can > be > * deduced by giving the reloption a special default value (e.g., > -2 is > * a common one for integer reloptions), but this isn't always > * possible. One notable example is Boolean reloptions, where it's > * difficult to discern the source of the value. This offset is > only > * used if given a value greater than zero. > */ > int isset_offset; > > > I didn't actually come back to this before writing my comment. I'm glad they both say basically the same thing. I'm still partial to mine but yours probably fits the overall style of the codebase better. David J.
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