Re: BUG #15791: WalSndCtl->sync_standbys_defined modified too late

From: Euler Taveira <euler(at)timbira(dot)com(dot)br>
To: 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-06 01:16:39
Message-ID: CAHE3wgjVViFz2FW6srodA5yc_rF+3t9GgHpaGAP+2qkn4XQa_Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Em dom, 5 de mai de 2019 às 05:57, PG Bug reporting form
<noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2019-05-06 01:46:08 Re: identity not working with inherited table
Previous Message Francisco Olarte 2019-05-05 11:15:57 Re: identity not working with inherited table