On Wed, May 27, 2026 at 5:39 PM Masahiko Sawada <[email protected]> wrote: > > I noticed that this point still remains as an open item for PG19. > > I agree with the points Andres and Amit made: the REPLICATION > privilege already grants very powerful capabilities, including the > ability to read all data via physical streaming and to hold back > horizons. A user trusted with REPLICATION is already trusted enough > that allowing them to create a logical slot does not represent a > fundamentally new class of risk. > > As Andres pointed out, any user with more than the bare minimum of > permissions can cause arbitrarily high WAL volume in hard-to-identify > ways. If the concern is about detecting and responding to unexpected > overhead the better path would be improving monitoring infrastructure > (e.g. per-session or per-user WAL tracking) rather than restricting > logical slot creation itself. And we already have backend-level WAL > statistics. Since there have been no further objections since then, > I'd like to propose closing this open item as "Non-bugs". >
+1. -- With Regards, Amit Kapila.
