Re: pg_dump --with-* options
Fujii Masao <masao.fujii@oss.nttdata.com>
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Nathan Bossart <nathandbossart@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jeff Davis <pgsql@j-davis.com>, Corey Huinker <corey.huinker@gmail.com>,
Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut
<peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-17T01:08:35Z
Lists: pgsql-hackers
On 2025/06/17 9:58, Nathan Bossart wrote: > On Mon, Jun 16, 2025 at 07:09:17PM -0400, Tom Lane wrote: >> I find myself increasingly persuaded by Corey's point of view ... > > +1 Can you clarify how using on-by-default would simplify things? I'm not sure it actually makes the options simpler. Regards, -- Fujii Masao NTT DATA Japan Corporation
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