Home > mailing lists

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

From	David G. Johnston
Subject	BUG #19379: Role pg_read_all_data don't allowed read large objects
Date	May 19 18:35:04
Msg-id	CAKFQuwZKmMVLxz993qOFXf=tivPBaWq=xosgCYRmuuU3UNsS+w@mail.gmail.com Whole thread
In response to	BUG #19379: Role pg_read_all_data don't allowed read large objects (PG Bug reporting form <noreply@postgresql.org>)
List	pgsql-bugs

Tree view

On Tuesday, May 19, 2026, Long76 <long76.git@mail.ru> wrote:

Hello, i waited 17.10 release with fix https://commitfest.postgresql.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.

pgsql-bugs by date:

From: surya poondla
Date: 18 May, 19:48:43
Subject: Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY

From: PG Bug reporting form
Date: 20 May, 12:23:35
Subject: BUG #19489: Function Name Conflict Between TimescaleDB and pg_stat_monitor Affecting Extension Upgrade

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

Previous

Next