Re: vacuumdb: add --dry-run

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: vacuumdb: add --dry-run
Date: 2025-12-05 20:34:12
Message-ID: CADkLM=f99AzFrdnPdo3PkO27rYtJv5WoGQXrq9Bf8_Y4vVxuBw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-12-05 20:47:38 Re: vacuumdb: add --dry-run
Previous Message Cary Huang 2025-12-05 20:12:50 Re: Support tid range scan in parallel?