public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Ron Johnson <[email protected]>
Cc: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: In-order pg_dump (or in-order COPY TO)
Date: Wed, 27 Aug 2025 10:42:57 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com>
Ron Johnson <[email protected]> writes:
> On Wed, Aug 27, 2025 at 10:16 AM Tom Lane <[email protected]> wrote:
>> Don't use --format=custom (and not -v either). That causes pg_dump to
>> include the OIDs and pg_dump object IDs of all the tables and other
>> objects,
> That's interesting. Why? (Since isn't it supposed to be Bad to rely on
> OIDs?)
-v in a text-format dump includes that data for debugging purposes:
--
-- TOC entry 1401 (class 1255 OID 16499)
-- Name: fipshash(text); Type: FUNCTION; Schema: public; Owner: postgres
--
(The "TOC entry" comment line wouldn't be there without -v.)
Then custom format has to store the same info so that pg_restore
can produce this identical text output on demand.
Yeah, this is all pretty historical, but nobody wants to change it
at this point.
regards, tom lane
view thread (4+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: In-order pg_dump (or in-order COPY TO)
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox