BUG #19379: Role pg_read_all_data don't allowed read large objects

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Long76 <long76(dot)git(at)mail(dot)ru>
Cc: Pierre Forstmann <pierre(dot)forstmann(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: BUG #19379: Role pg_read_all_data don't allowed read large objects
Date: 2026-05-19 15:35:04
Message-ID: CAKFQuwZKmMVLxz993qOFXf=tivPBaWq=xosgCYRmuuU3UNsS+w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tuesday, May 19, 2026, Long76 <long76(dot)git(at)mail(dot)ru> 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.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Anton Fedorov 2026-05-19 20:44:33 Fwd: Non-cancellable queries
Previous Message PG Bug reporting form 2026-05-19 11:06:06 BUG #19488: Standby connection fails after dropping on login event trigger enabled always