Re: POC: enable logical decoding when wal_level = 'replica' without a server restart

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: POC: enable logical decoding when wal_level = 'replica' without a server restart
Date: 2026-06-01 16:41:07
Message-ID: CAD21AoAY1RBA0rVNQ74TtBPeq6uYFwcdrW4qYbytCEUwx_2Szw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 28, 2026 at 8:17 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> On Wed, May 27, 2026 at 5:39 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> 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.

I've moved it to "Non-bugs".

Regards,

--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-06-01 16:44:28 Re: Fix race during concurrent logical decoding activation
Previous Message Joel Jacobson 2026-06-01 16:20:48 Re: should we have a fast-path planning for OLTP starjoins?