Re: pg_dump --with-* options

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump --with-* options
Date: 2025-06-14 02:42:05
Message-ID: CADkLM=e3-EYvq4jadquxUEP=0o+m4pYdcRgwNw8kTYP2duk6ug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> Good point. Now that we are getting rid of some of the other options,
> we don't need to worry about consistency with them, and I think we
> should just use "--statistics".

The point of the --with flags was to future proof commands to preserve
behavior in case the defaults ever changed.

This would all be a lot simpler, and the --with switches would all be
unnecessary, if we didn't decide to make exactly one type of dumpable
object (statistics) off by default but only in one of the three commands
(pg_dump).

I think we're creating lasting confusion for the sake of short-term
convenience.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-06-14 03:27:41 Re: Add a bound check to TidRangeEval
Previous Message Corey Huinker 2025-06-14 02:29:35 Re: pg_dump --with-* options