Re: pg_dump --with-* options - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pg_dump --with-* options
Date
Msg-id CA+TgmoYuP7TvwThJERO2X7CHJCrTMpiv=Fd=EPOcyWwL=8J4Hg@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump --with-* options  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On Tue, Jun 24, 2025 at 12:48 PM Nathan Bossart
<nathandbossart@gmail.com> wrote:
> On Mon, Jun 23, 2025 at 01:38:10PM -0400, Robert Haas wrote:
> > I had thought we had a consensus that pg_upgrade should preserve stats
> > but regularly pg_dump shouldn't include them; perhaps I misunderstood
> > or that changed.
>
> I think it's a bit of both.  I skimmed through the past discussions and
> found that not only was there a rough consensus in 2024 that stats _should_
> be on by default [0], but also that an updated vote tally didn't show much
> of a consensus at all [1].  Like you, I thought we had pretty much closed
> that door, but the aforementioned analysis along with further discussion
> has me convinced that we might want to reconsider [2].

Well, I don't know: I still think that's the right answer, so I don't
really want to reconsider, but I understand that I'm not in charge
here.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: problems with toast.* reloptions
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] Fix OAuth feature detection on OpenBSD+Meson