Postgres Pro
Downloads
Home   >   mailing lists

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

From Euler Taveira
Subject Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late
Date
Msg-id CAHE3wgjVViFz2FW6srodA5yc_rF+3t9GgHpaGAP+2qkn4XQa_Q@mail.gmail.com
Whole thread Raw
In response to BUG #15791: WalSndCtl->sync_standbys_defined modified too late  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Tree view 
Em dom, 5 de mai de 2019 às 05:57, PG Bug reporting form
<noreply@postgresql.org> escreveu:
>
> when modify synchronous_standby_names in postgres.conf, and no checkpoint
> happenes, will  synchronous_standby_names  take effect?
>
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)'.


--
   Euler Taveira                                   Timbira -
http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

pgsql-bugs by date:

Previous
From: Francisco Olarte
Date:
Subject: Re: identity not working with inherited table
Next
From: Euler Taveira
Date:
Subject: Re: identity not working with inherited table