| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | 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-11-20 22:16:13 |
| Message-ID: | aR-TLculrOb2hbRy@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 20, 2025 at 05:09:54PM -0500, Corey Huinker wrote:
> I have no objections to, but I am curious about the factors that went into
> making dry_run an independent boolean rather than part of vacopts.
My thinking was that it's closer to "echo" and "quiet" than anything in
vacuumingOptions. Most of that stuff seems geared towards controlling the
precise behavior of the commands rather than the behavior of the
application. TBH I think it'd be fine either way. We could probably even
move "echo" and "quiet" into vacuumingOptions if we really wanted to.
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-11-20 22:17:16 | Re: Eagerly evict bulkwrite strategy ring |
| Previous Message | David Rowley | 2025-11-20 22:12:32 | Re: another autovacuum scheduling thread |