Re: vacuumdb: add --dry-run

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>

To: Nathan Bossart <nathandbossart@gmail.com>

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

Date: 2025-12-08T18:23:16Z

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 2025-Dec-08, Nathan Bossart wrote:

> On Sat, Dec 06, 2025 at 07:48:22AM +0800, Chao Li wrote:

> > ```
> > +	if (vacopts.dry_run)
> > +		pg_log_info("Executing in dry-run mode.”);
> > ```
> > 
> > Feels like “Running” is better than “Executing”.
> 
> Done.

I haven't read this thread, but chanced to come across this and wanted
to note recent commit c05dee191125.  I'm not opposed to changing what
went in there, but let's make them all the same.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/