Re: BUG #19379: Role pg_read_all_data don't allowed read large objects - Mailing list pgsql-bugs

From Nitin Motiani
Subject Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
Date
Msg-id CAH5HC97jzTH-ig-w0C=X-zm8qXSACKf2UxuT8Mzo4c4Nmn1z9Q@mail.gmail.com
Whole thread
In response to Re: BUG #19379: Role pg_read_all_data don't allowed read large objects  (Andres Freund <andres@anarazel.de>)
List pgsql-bugs
On Thu, Jan 15, 2026 at 7:15 PM Andres Freund <andres@anarazel.de> wrote:
>
> >
> > The docs you link note that all data is “tables, views, sequences”.  Large
> > objects are not listed.  Maybe that means the name is a bit misleading but
> > it’s working as documented.
> >
> > Likewise, the LO page doesn’t 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_nDABH5c4w2MDfyx4vEWxBEfofGWsw%40mail.gmail.com



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19392: PG_UPGRADE is non-functional on Windows
Next
From: PG Bug reporting form
Date:
Subject: BUG #19394: error in ecpg