Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late
Date
Msg-id 20190507033745.GJ1499@paquier.xyz
Whole thread Raw
In response to Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late  (Euler Taveira <euler@timbira.com.br>)
List pgsql-bugs
On Sun, May 05, 2019 at 10:16:39PM -0300, Euler Taveira wrote:
> This is not a bug. This question is suitable for -hackers.
>
> Short answer is: yes. When you modify synchronous_standby_names and
> reload postgresql.conf, checkpointer get SIGHUP and it calls
> UpdateSharedMemoryConfig() -- see CheckpointerMain() circa 'if
> (got_SIGHUP)'.

There could be always some delay between the moments SIGHUP gets
processed across the different processes as we are talking mainly
about running ProcessConfigFile(OGC_SIGHUP) which can happen for
normal backends once every query, but the change will be effective.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #15745: WAL References Invalid Pages...that eventuallyresolves
Next
From: PG Bug reporting form
Date:
Subject: BUG #15793: Required Community Version Installs not the customized EnterpriseDB one.