Horton
Menu

Re: pg_dump --with-* options

Jeff Davis <pgsql@j-davis.com>

View thread
From: Jeff Davis <pgsql@j-davis.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-07-29T18:24:54Z
Lists: pgsql-hackers 
On Wed, 2025-06-18 at 10:21 -0700, Jeff Davis wrote:
> On Wed, 2025-06-18 at 10:43 -0500, Nathan Bossart wrote:
> > IIUC the current proposal is to:
> > 
> > * Dump/restore stats by default.

We don't have a consensus for that, so unless a few people make an
abrupt turnaround, this will remain off for v18.

> > * Keep the --no-statistics, --no-schema, and --no-data options.
> > * Keep the --statistics-only, --schema-only, and --data-only
> > options.
> > * Remove the --with-statistics, --with-schema, and --with-data
> > options.

The other parts of the proposal are very similar with mine below:

>   * delete the --with-data and --with-schema options as unnecessary
>   * (maybe?) rename --with-statistics to --statistics
>   * keep --no-statistics, --no-data, --no-schema (or use "without"
> instead?)
>   * (maybe?) keep --statistics-only
>   * reject the combination of an "only" option and a "with" option

The main difference is whether we:

  (a) keep both --statistics and --no-statistics in pg_dump and
pg_restore; or

  (b) for pg_dump have --statistics but not --no-statistics and for
pg_restore have --no-statistics but not --statistics.

Option (a) creates redundancies whereas (b) creates a divergence. I
suppose I prefer (a), but I don't have a terribly strong opinion and if
more people prefer (b) then I'll go with that.

Regards,
	Jeff Davis

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Simplify options in pg_dump and pg_restore.

  2. pg_dump: reject combination of "only" and "with"

  3. Change pg_dump default for statistics export.