Re: vacuumdb: add --dry-run - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: vacuumdb: add --dry-run
Date
Msg-id aTNE6gCmTwtMzomK@nathan
Whole thread Raw
In response to Re: vacuumdb: add --dry-run  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
On Fri, Dec 05, 2025 at 03:34:12PM -0500, Corey Huinker wrote:
>> I guess we could probably remove the top-level "Executing in dry-run mode"
>> message, provided we say the same thing in the per-database message.
>> However, the latter can be turned off with --quiet.  Maybe we should
>> consider disallowing --quiet and --dry-run.
> 
> --quiet does appear to be the sworn enemy of "tell me what you would have
> done if you were really gonna do it". So yeah, disallowing that combination
> would make sense.

On the other hand, --quiet is handy if you're trying to save the output of
--dry-run elsewhere to run later.  (Of course, if you use --all, that
output won't be tremendously useful.)

-- 
nathan



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: vacuumdb: add --dry-run
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] Allow complex data for GUC extra.