| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | 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 08:46:39 |
| Message-ID: | OSCPR01MB149667D5EF376E24A16E0429BF5E9A@OSCPR01MB14966.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2025-10-16 09:13:35 | Re: Inconsistent Behavior of GROUP BY ROLLUP in v17 vs master |
| Previous Message | Jim Jones | 2025-10-16 08:45:53 | Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement |