public inbox for [email protected]
help / color / mirror / Atom feedRe: BUG #19379: Role pg_read_all_data don't allowed read large objects
4+ messages / 4 participants
[nested] [flat]
* Re: BUG #19379: Role pg_read_all_data don't allowed read large objects
@ 2026-01-15 13:47 Pierre Forstmann <[email protected]>
0 siblings, 2 replies; 4+ messages in thread
From: Pierre Forstmann @ 2026-01-15 13:47 UTC (permalink / raw)
To: David G. Johnston <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>
It could be interesting to have a new predefined role pg_read_all_lo to
be able to read all LO.
Maybe it could be done with an extension with some background task to
take into account newly created LO but it should be easier to have this
coded without an extension.
Le 15/01/2026 à 14:36, David G. Johnston a écrit :
> 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/predefined-roles.html;
> https://www.postgresql.org/docs/17/lo-implementation.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[2]: BUG #19379: Role pg_read_all_data don't allowed read large objects
@ 2026-01-15 14:05 Глеб Борков <[email protected]>
parent: Pierre Forstmann <[email protected]>
1 sibling, 0 replies; 4+ messages in thread
From: Глеб Борков @ 2026-01-15 14:05 UTC (permalink / raw)
To: Pierre Forstmann <[email protected]>; +Cc: David G. Johnston <[email protected]>; [email protected]
Thanks for answers. And maybe pg_read_all_data without read lo don't allow read all data because need read data from lo. It's makes role pg_read_all_data useless. I hope for a speedy fix. четверг, 15 января 2026г., 16:47 +03:00 от Pierre Forstmann [email protected] :
>It could be interesting to have a new predefined role
> pg_read_all_lo to be able to read all LO.
>Maybe it could be done with an extension with some background
> task to take into account newly created LO but it should be easier
> to have this coded without an extension.
>Le 15/01/2026 à 14:36, David G.
> Johnston a écrit :
>>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 15:56 Long76 <[email protected]>
parent: Pierre Forstmann <[email protected]>
1 sibling, 1 reply; 4+ messages in thread
From: Long76 @ 2026-01-15 15:56 UTC (permalink / raw)
To: Pierre Forstmann <[email protected]>; +Cc: David G. Johnston <[email protected]>; [email protected] <[email protected]>
Thanks for answers.
Maybe pg_read_all_data without read lo don't allow read all data because need read lo.It's makes role pg_read_all_data useless.
I hope for a speedy fix.
>Четверг, 15 января 2026, 16:47 +03:00 от Pierre Forstmann < [email protected] >:
>
>It could be interesting to have a new predefined role pg_read_all_lo to be able to read all LO.
>Maybe it could be done with an extension with some background task to take into account newly created LO but it should be easier to have this coded without an extension.
>Le 15/01/2026 à 14:36, David G. Johnston a écrit :
>>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.
>>
--
Long76
^ permalink raw reply [nested|flat] 4+ messages in thread
* BUG #19379: Role pg_read_all_data don't allowed read large objects
@ 2026-05-19 15:35 David G. Johnston <[email protected]>
parent: Long76 <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: David G. Johnston @ 2026-05-19 15:35 UTC (permalink / raw)
To: Long76 <[email protected]>; +Cc: Pierre Forstmann <[email protected]>; [email protected] <[email protected]>
On Tuesday, May 19, 2026, Long76 <[email protected]> wrote:
> Hello, i waited 17.10 release with fix https://commitfest.postgre
> sql.org/patch/6485/ but seems it wasn’t backported. Why? It’s will be
> fixed only in 19 version?
>
It does not qualify as something that can be back-ported. It is an
entirely new behavior. The existing behaviors, while maybe not ideal, are
working as documented.
David J.
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2026-05-19 15:35 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-01-15 13:47 Re: BUG #19379: Role pg_read_all_data don't allowed read large objects Pierre Forstmann <[email protected]>
2026-01-15 14:05 ` Re[2]: BUG #19379: Role pg_read_all_data don't allowed read large objects Глеб Борков <[email protected]>
2026-01-15 15:56 ` Long76 <[email protected]>
2026-05-19 15:35 ` David G. Johnston <[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