| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(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:47:38 |
| Message-ID: | aTNE6gCmTwtMzomK@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-12-05 20:48:32 | Re: [PATCH] Allow complex data for GUC extra. |
| Previous Message | Corey Huinker | 2025-12-05 20:34:12 | Re: vacuumdb: add --dry-run |