Re: vacuumdb: add --dry-run

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>

To: Chao Li <li.evan.chao@gmail.com>

Cc: Álvaro Herrera <alvherre@kurilemu.de>, Corey Huinker <corey.huinker@gmail.com>, pgsql-hackers@postgresql.org

Date: 2025-12-09T19:42: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 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 Tue, Dec 09, 2025 at 07:04:24AM +0800, Chao Li wrote:
> I searched over the source tree, and find “Running in xxx mode” in initdb
> and option.c:
> 
> [...]
> 
> And “”Executing in dry-run mode” in a few commands: pg_archivecleanup.c,
> pg_createsubscriber.c, pg_combinebackup.c and pg_rewind.c.
> 
> Should we make them all consistent?

I think both phrasings clearly convey the information just fine.

-- 
nathan