Re: vacuumdb: add --dry-run

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>

To: Corey Huinker <corey.huinker@gmail.com>

Cc: Chao Li <li.evan.chao@gmail.com>, pgsql-hackers@postgresql.org

Date: 2025-11-20T22:16:13Z

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 ParallelSlotSetIdle().
- 750816971b35 19 (unreleased) landed
vacuumdb: Add --dry-run.
- d107176d27c7 19 (unreleased) landed
vacuumdb: Move some variables to the vacuumingOptions struct.
- cf1450e57799 19 (unreleased) landed
Log a note at program start when running in dry-run mode
- c05dee191125 19 (unreleased) cited

On Thu, Nov 20, 2025 at 05:09:54PM -0500, Corey Huinker wrote:
> I have no objections to, but I am curious about the factors that went into
> making dry_run an independent boolean rather than part of vacopts.

My thinking was that it's closer to "echo" and "quiet" than anything in
vacuumingOptions.  Most of that stuff seems geared towards controlling the
precise behavior of the commands rather than the behavior of the
application.  TBH I think it'd be fine either way.  We could probably even
move "echo" and "quiet" into vacuumingOptions if we really wanted to.

-- 
nathan