Re: pg_dump --with-* options

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Jeff Davis <pgsql@j-davis.com>, Nathan Bossart <nathandbossart@gmail.com>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-06-12T19:16:19Z

Lists: pgsql-hackers

On 12.06.25 17:14, Jeff Davis wrote:
> On Thu, 2025-06-12 at 15:47 +0200, Peter Eisentraut wrote:
>> My initial guess was that --with-data can override --no-data.  That
>> would have been pretty standard "last option wins" behavior.  But
>> pg_dump rejects that.  Personally, I think that is kind of wrong.
> 
> Do we have other options that are order-sensitive?

I think most of them are.  For example:

psql -p 5432 -p 5433
initdb --data-checksums --no-data-checksums
postgres --shared-buffers=1GB --shared-buffers=2GB

Commits

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

Simplify options in pg_dump and pg_restore.
- 6a46089e458f 19 (unreleased) landed
- a3e8dc143862 18.0 landed
pg_dump: reject combination of "only" and "with"
- 0ed92cf50cc4 19 (unreleased) landed
- 60121890f7f2 18.0 landed
Change pg_dump default for statistics export.
- 34eb2a80d5a3 18.0 cited