Horton
Menu

Re: pg_dump --with-* options

Corey Huinker <corey.huinker@gmail.com>

View thread
From: Corey Huinker <corey.huinker@gmail.com>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Jeff Davis <pgsql@j-davis.com>, Nathan Bossart <nathandbossart@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-14T02:29:35Z
Lists: pgsql-hackers 
>
> One of the challenges in the current case is that it is not obvious how
> --with-data, --no-data, --data-only etc. are connected.  If that were
> clearer, then the way these options should combine or conflict would
> hopefully follow somewhat naturally.
>

They all should be mutually exclusive, and usage of any two of them should
raise an error, hence order not mattering.

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.