MIME-Version: 1.0
References: <s0491qrn-343s-0757-8sn5-120rr8610qqq@tzk.arg> <daf47435-539f-4368-869c-dd19a341399b@aklaver.com>
 <3541781s-75o7-26pp-46pp-qs54o4406192@tzk.arg> <1389082.1756304193@sss.pgh.pa.us>
 <CANzqJaAYu6ff9KqrEqU==JMNErGqszC__SZuZp1Wnwz=nFkXWQ@mail.gmail.com> <1392027.1756305777@sss.pgh.pa.us>
In-Reply-To: <1392027.1756305777@sss.pgh.pa.us>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Wed, 27 Aug 2025 11:12:50 -0400
Message-ID: <CANzqJaAO1qzsMxUPm2z-JnZxGTUpopbC3TQ8Dq9NDo2A+a0miw@mail.gmail.com>
Subject: Re: In-order pg_dump (or in-order COPY TO)
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000089f07e063d5a3933"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaAO1qzsMxUPm2z-JnZxGTUpopbC3TQ8Dq9NDo2A%2Ba0miw%40mail.gmail.com>
Precedence: bulk

--00000000000089f07e063d5a3933
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 27, 2025 at 10:42=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> wrote=
:

> Ron Johnson <ronljohnsonjr@gmail.com> writes:
> > On Wed, Aug 27, 2025 at 10:16=E2=80=AFAM Tom Lane <tgl@sss.pgh.pa.us> w=
rote:
> >> Don't use --format=3Dcustom (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 o=
n
> > 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.
>

Ah, so the culprit is "-v".  I like using -v, redirecting it to a log file
(more info is almost always better), but then I rarely use pg_dump, and
never pipe it to de-duplicators.  (ExaGrid is supposed to deduplicate, but
that's not going to stop me from using pgbackrest, compression and
encryption; PCI auditors care about that, not deduplication.)

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

--00000000000089f07e063d5a3933
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Wed, Aug 27, 2025 at 10:42=E2=80=AFAM =
Tom Lane &lt;<a href=3D"mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt;=
 wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">Ron Johnson &lt;<a href=3D"mailto:ronl=
johnsonjr@gmail.com" target=3D"_blank">ronljohnsonjr@gmail.com</a>&gt; writ=
es:<br>
&gt; On Wed, Aug 27, 2025 at 10:16=E2=80=AFAM Tom Lane &lt;<a href=3D"mailt=
o:tgl@sss.pgh.pa.us" target=3D"_blank">tgl@sss.pgh.pa.us</a>&gt; wrote:<br>
&gt;&gt; Don&#39;t use --format=3Dcustom (and not -v either).=C2=A0 That ca=
uses pg_dump to<br>
&gt;&gt; include the OIDs and pg_dump object IDs of all the tables and othe=
r<br>
&gt;&gt; objects,<br>
<br>
&gt; That&#39;s interesting.=C2=A0 Why?=C2=A0 (Since isn&#39;t it supposed =
to be Bad to rely on<br>
&gt; OIDs?)<br>
<br>
-v in a text-format dump includes that data for debugging purposes:<br>
<br>
--<br>
-- TOC entry 1401 (class 1255 OID 16499)<br>
-- Name: fipshash(text); Type: FUNCTION; Schema: public; Owner: postgres<br=
>
--<br>
<br>
(The &quot;TOC entry&quot; comment line wouldn&#39;t be there without -v.)<=
br>
Then custom format has to store the same info so that pg_restore<br>
can produce this identical text output on demand.<br></blockquote><div><br>=
</div><div></div></div><div>Ah, so the culprit is &quot;-v&quot;.=C2=A0 I l=
ike using -v, redirecting it to a log file (more info is almost always bett=
er), but then I rarely use pg_dump, and never pipe it to de-duplicators.=C2=
=A0 (ExaGrid is supposed to deduplicate, but that&#39;s not going to stop m=
e from using pgbackrest, compression and encryption; PCI auditors care abou=
t that, not deduplication.)</div><div><br></div><span class=3D"gmail_signat=
ure_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div d=
ir=3D"ltr">Death to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t boil =
me, I&#39;m still alive.<br><div><div>&lt;Redacted&gt; lobster!</div></div>=
</div></div></div></div>

--00000000000089f07e063d5a3933--