Re: Statistics Import and Export - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Statistics Import and Export
Date
Msg-id CAKAnmmKzJQxWLmkBTgCZ-N_0SonudWxbmAq=cwbV-wz83JoFNA@mail.gmail.com
Whole thread Raw
In response to Re: Statistics Import and Export  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Statistics Import and Export
List pgsql-hackers
On Sat, Mar 1, 2025 at 4:23 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
That particular argument needs to be rejected vociferously.

Okay, I will concede that part of my argument. And for the record, I've written pg_dump output parsing programs many times over the years, and seen others in the wild. It's not uncommon as some in this thread think.
 
What other part of pg_dump's output is not produced by default?

None, but that's kind of the point - this is a very special class of data (so much so, that we've been arguing about where it fits in our usual pre/data/post paradigm). So I don't think it's unreasonable that something this unique (and non-deterministic) gets excluded by default. It's still only a flag away if people require it.

Cheers,
Greg

--
Enterprise Postgres Software Products & Tech Support

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PATCH: warn about, and deprecate, clear text passwords
Next
From: Masahiko Sawada
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations