Re: pg_dump --with-* options
| От | Nathan Bossart |
|---|---|
| Тема | Re: pg_dump --with-* options |
| Дата | |
| Msg-id | aFCIB1AwXuNzxHXX@nathan обсуждение исходный текст |
| Ответ на | Re: pg_dump --with-* options (Corey Huinker <corey.huinker@gmail.com>) |
| Ответы |
Re: pg_dump --with-* options
|
| Список | 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
В списке pgsql-hackers по дате отправления: