MIME-Version: 1.0
References: <19379-089536632927293f@postgresql.org> <CAKFQuwZbtoAs1Ew62aC25R1r7i=M1J_3UmCsssidwDn2Xe6XhA@mail.gmail.com>
 <r5a3aqlrrqen2snktdmx5tjeoakp3hmbektlqmeqhij3fqqez4@zmx3bdscipny>
In-Reply-To: <r5a3aqlrrqen2snktdmx5tjeoakp3hmbektlqmeqhij3fqqez4@zmx3bdscipny>
From: Nitin Motiani <nitinmotiani@google.com>
Date: Thu, 5 Feb 2026 15:35:26 +0530
Message-ID: <CAH5HC97jzTH-ig-w0C=X-zm8qXSACKf2UxuT8Mzo4c4Nmn1z9Q@mail.gmail.com>
Subject: Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
To: Andres Freund <andres@anarazel.de>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, "long76.git@mail.ru" <long76.git@mail.ru>, 
	"pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/CAH5HC97jzTH-ig-w0C%3DX-zm8qXSACKf2UxuT8Mzo4c4Nmn1z9Q%40mail.gmail.com>
Precedence: bulk

On Thu, Jan 15, 2026 at 7:15=E2=80=AFPM Andres Freund <andres@anarazel.de> =
wrote:
>
> >
> > The docs you link note that all data is =E2=80=9Ctables, views, sequenc=
es=E2=80=9D.  Large
> > objects are not listed.  Maybe that means the name is a bit misleading =
but
> > it=E2=80=99s working as documented.
> >
> > Likewise, the LO page doesn=E2=80=99t say anything about read all being=
 applicable.
>
> It's not contradicting our docs, but I think it likely still is an
> oversight. The goal of pg_read_all_data [1] was to allow running pg_dump
> without having to grant granular access, not being able to run pg_dump
> successfully due to LOs prevents that.
>

Hi,

I have proposed a fix for this on pgsql-hackers [1]. And tested that
with the fix, pg_read_all_data can dump large objects. Please take a
look and let me know what you think.

Thanks & Regards,
Nitin Motiani
Google

[1] https://www.postgresql.org/message-id/CAH5HC96dxAEvP78s1-JK_nDABH5c4w2M=
Dfyx4vEWxBEfofGWsw%40mail.gmail.com