public inbox for [email protected]help / color / mirror / Atom feed
BUG #19379: Role pg_read_all_data don't allowed read large objects 4+ messages / 4 participants [nested] [flat]
* BUG #19379: Role pg_read_all_data don't allowed read large objects @ 2026-01-15 11:57 PG Bug reporting form <[email protected]> 2026-01-15 13:36 ` BUG #19379: Role pg_read_all_data don't allowed read large objects David G. Johnston <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: PG Bug reporting form @ 2026-01-15 11:57 UTC (permalink / raw) To: [email protected]; +Cc: [email protected] The following bug has been logged on the website: Bug reference: 19379 Logged by: Misha Shaygu Email address: [email protected] PostgreSQL version: 17.7 Operating system: Kubuntu 24.04 Description: My goal: create role for backup any database on server Steps: 1. CREATE USER backup_user; 2. GRANT pg_read_all_data TO backup_user; 3. pg_dump my_db 4. got error to read large object Following by links https://www.postgresql.org/docs/17/predefined-roles.html https://www.postgresql.org/docs/17/lo-implementation.html "SELECT privileges are required to read a large object" and role "pg_read_all_data" grant it, but it don't work! Please fix it, thanks! ^ permalink raw reply [nested|flat] 4+ messages in thread
* BUG #19379: Role pg_read_all_data don't allowed read large objects 2026-01-15 11:57 BUG #19379: Role pg_read_all_data don't allowed read large objects PG Bug reporting form <[email protected]> @ 2026-01-15 13:36 ` David G. Johnston <[email protected]> 2026-01-15 13:45 ` Re: BUG #19379: Role pg_read_all_data don't allowed read large objects Andres Freund <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: David G. Johnston @ 2026-01-15 13:36 UTC (permalink / raw) To: [email protected] <[email protected]>; [email protected] <[email protected]> On Thursday, January 15, 2026, PG Bug reporting form <[email protected]> wrote: > The following bug has been logged on the website: > > Bug reference: 19379 > Logged by: Misha Shaygu > Email address: [email protected] > PostgreSQL version: 17.7 > Operating system: Kubuntu 24.04 > Description: > > My goal: create role for backup any database on server > > Steps: > 1. CREATE USER backup_user; > 2. GRANT pg_read_all_data TO backup_user; > 3. pg_dump my_db > 4. got error to read large object > > Following by links > https://www.postgresql.org/docs/17/predefined-roles.html > https://www.postgresql.org/docs/17/lo-implementation.html > "SELECT privileges are required to read a large object" and role > "pg_read_all_data" grant it, but it don't work! > > Please fix it, thanks! > 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. David J. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #19379: Role pg_read_all_data don't allowed read large objects 2026-01-15 11:57 BUG #19379: Role pg_read_all_data don't allowed read large objects PG Bug reporting form <[email protected]> 2026-01-15 13:36 ` BUG #19379: Role pg_read_all_data don't allowed read large objects David G. Johnston <[email protected]> @ 2026-01-15 13:45 ` Andres Freund <[email protected]> 2026-02-05 10:05 ` Re: BUG #19379: Role pg_read_all_data don't allowed read large objects Nitin Motiani <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Andres Freund @ 2026-01-15 13:45 UTC (permalink / raw) To: David G. Johnston <[email protected]>; +Cc: [email protected] <[email protected]>; [email protected] <[email protected]> Hi, On 2026-01-15 06:36:35 -0700, David G. Johnston wrote: > On Thursday, January 15, 2026, PG Bug reporting form <[email protected]> > wrote: > > > The following bug has been logged on the website: > > > > Bug reference: 19379 > > Logged by: Misha Shaygu > > Email address: [email protected] > > PostgreSQL version: 17.7 > > Operating system: Kubuntu 24.04 > > Description: > > > > My goal: create role for backup any database on server > > > > Steps: > > 1. CREATE USER backup_user; > > 2. GRANT pg_read_all_data TO backup_user; > > 3. pg_dump my_db > > 4. got error to read large object > > > > Following by links > > https://www.postgresql.org/docs/17/predefined-roles.html > > https://www.postgresql.org/docs/17/lo-implementation.html > > "SELECT privileges are required to read a large object" and role > > "pg_read_all_data" grant it, but it don't work! > > > > Please fix it, thanks! > > > > 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. This doesn't seem like something we're going to fix in a minor version though... Greetings, Andres Freund [1] http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=6c3ffd697e2242f5497ea4b40fffc8f6f922ff... > A commonly requested use-case is to have a role who can run an > unfettered pg_dump without having to explicitly GRANT that user access > to all tables, schemas, et al, without that role being a superuser. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: BUG #19379: Role pg_read_all_data don't allowed read large objects 2026-01-15 11:57 BUG #19379: Role pg_read_all_data don't allowed read large objects PG Bug reporting form <[email protected]> 2026-01-15 13:36 ` BUG #19379: Role pg_read_all_data don't allowed read large objects David G. Johnston <[email protected]> 2026-01-15 13:45 ` Re: BUG #19379: Role pg_read_all_data don't allowed read large objects Andres Freund <[email protected]> @ 2026-02-05 10:05 ` Nitin Motiani <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Nitin Motiani @ 2026-02-05 10:05 UTC (permalink / raw) To: Andres Freund <[email protected]>; +Cc: David G. Johnston <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]> On Thu, Jan 15, 2026 at 7:15 PM Andres Freund <[email protected]> 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.gma... ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2026-02-05 10:05 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-01-15 11:57 BUG #19379: Role pg_read_all_data don't allowed read large objects PG Bug reporting form <[email protected]> 2026-01-15 13:36 ` David G. Johnston <[email protected]> 2026-01-15 13:45 ` Andres Freund <[email protected]> 2026-02-05 10:05 ` Nitin Motiani <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox