Re: pg_dump --with-* options
Nathan Bossart <nathandbossart@gmail.com>
From: Nathan Bossart <nathandbossart@gmail.com>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>, Jeff Davis <pgsql@j-davis.com>, Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-16T21:09:27Z
Lists: pgsql-hackers
On Mon, Jun 16, 2025 at 03:35:48PM -0400, Corey Huinker wrote: > I think this is the exact sort of confusion caused by having two of the > three types default to on in all circumstances, and one default to off in > one special circumstance. I revisited the main thread to see how folks voted. There are a lot of messages over a long period of time, and folks may have changed their mind since, but this is what I saw: off-by-default: Mullane, Haas, Davis, Bossart on-by-default: Huinker, Lane, Hagander, Frost In fact, there seems to have been general agreement in 2024 that stats _should_ be on by default [0]. So perhaps there's not as strong of a consensus as we thought. Maybe we should ask for any new/updated votes. > Let's keep this simple, and have all three types default to on in all > circumstances. Assuming we did turn on stats by default, what is the minimum set of new flags in v18 you'd like to see? [0] https://postgr.es/m/e16cd9caf4f5229a152d318d70b4d323a03e3539.camel%40j-davis.com -- nathan
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