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

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(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: 2025-10-16 17:41:36
Message-ID: CAD21AoBBHKKAUW=DH5wUkwqi90yynRC5gHp0X5WuZLmMqTJHBA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 16, 2025 at 1:46 AM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear Sawada-san,
>
> > It's not harmful in practice. I've considered waking up the postmaster
> > with a new PMSignalReason, but I thought it's overkill to introduce a
> > new reason just to wake up the postmaster. If there is a convenient
> > way, I'd like to use that.
>
> It's not straightforward, but can we reuse SIGHUP signal for the purpose? This
> operation actually modifies the GUC parameter wal_level. One downside is that
> postmaster will propagated it to all processes, which is not required.

I think there is a big drawback that the server ends up reloading all
other GUC parameters, which might not be an expected timing for users.

Regards,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-10-16 17:46:49 Optimizing ResouceOwner to speed up COPY
Previous Message Jacob Champion 2025-10-16 17:40:10 Re: anonymous unions (C11)