MIME-Version: 1.0
From: "Radoulov, Dimitre" <cichomitiko@gmail.com>
Date: Thu, 4 Dec 2025 13:12:50 +0100
Message-ID: 
 <CAGJBphSX2oMPPu=VM4U8NP4+qffFH_483tFQCJ_s-mOcN3DLDw@mail.gmail.com>
Subject: Documentation clarification request: pg_dumpall and Large Objects
To: pgsql-docs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000094b0b06451f405e"
Archived-At: 
 <https://www.postgresql.org/message-id/CAGJBphSX2oMPPu%3DVM4U8NP4%2BqffFH_483tFQCJ_s-mOcN3DLDw%40mail.gmail.com>
Precedence: bulk

--000000000000094b0b06451f405e
Content-Type: text/plain; charset="UTF-8"

Hello,

I would like to request a clarification in the pg_dumpall
documentation regarding Large Objects (LOBs). The current
documentation does not explicitly state whether pg_dumpall includes
Large Objects in its output.

In the source code (pg_dumpall.c), there is a comment indicating
that pg_dumpall forces all pg_dump output to plain text. Since Large
Objects are only included by pg_dump when using -b or non-text
archive formats (custom/tar), pg_dumpall cannot include LOBs in its
output.

This behavior is clear from the implementation, but not from the
documentation.

I propose adding an explicit note such as:

  "pg_dumpall does not include Large Objects (BLOBs). To back up
   Large Objects, use pg_dump -b per database."

This clarification would help prevent user confusion during
cluster-wide backup procedures.

Thank you.

Best regards,
Dimitre Radoulov

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

<div dir=3D"auto"><div dir=3D"auto">Hello,</div><div dir=3D"auto"><br></div=
><div dir=3D"auto">I would like to request a clarification in the pg_dumpal=
l</div><div dir=3D"auto">documentation regarding Large Objects (LOBs). The =
current</div><div dir=3D"auto">documentation does not explicitly state whet=
her pg_dumpall includes</div><div dir=3D"auto">Large Objects in its output.=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">In the source code (pg_=
dumpall.c), there is a comment indicating</div><div dir=3D"auto">that pg_du=
mpall forces all pg_dump output to plain text. Since Large</div><div dir=3D=
"auto">Objects are only included by pg_dump when using -b or non-text</div>=
<div dir=3D"auto">archive formats (custom/tar), pg_dumpall cannot include L=
OBs in its</div><div dir=3D"auto">output.</div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">This behavior is clear from the implementation, but not f=
rom the</div><div dir=3D"auto">documentation.</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">I propose adding an explicit note such as:</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">=C2=A0 &quot;pg_dumpall does not i=
nclude Large Objects (BLOBs). To back up</div><div dir=3D"auto">=C2=A0 =C2=
=A0Large Objects, use pg_dump -b per database.&quot;</div><div dir=3D"auto"=
><br></div><div dir=3D"auto">This clarification would help prevent user con=
fusion during</div><div dir=3D"auto">cluster-wide backup procedures.</div><=
div dir=3D"auto"><br></div><div dir=3D"auto">Thank you.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">Best regards,</div><div dir=3D"auto">Dimitr=
e Radoulov=C2=A0</div></div>

--000000000000094b0b06451f405e--