| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
| Cc: | zhq651(at)126(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late |
| Date: | 2019-05-07 03:37:45 |
| Message-ID: | 20190507033745.GJ1499@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2019-05-07 06:56:22 | BUG #15793: Required Community Version Installs not the customized EnterpriseDB one. |
| Previous Message | Michael Paquier | 2019-05-07 03:34:22 | Re: BUG #15745: WAL References Invalid Pages...that eventually resolves |