Re: Parameter status message not sent?

2018-02-13 Thread Tatsuo Ishii
> It'll only get sent to the client the next time the server processes a > query. We can't just at arbitrary points reload the config file or send > messages out. The SIGHUP handler just sets ConfigReloadPending which > PostgresMain() then processes: > > /* >* (6)

Re: Parameter status message not sent?

2018-02-13 Thread Andres Freund
Hi, On 2018-02-14 10:42:12 +0800, Craig Ringer wrote: > I was wondering a while ago - can't we just set our own proc's latch here, > so we wake up and send it earlier if we're in the idle main loop? The problem is that the client doesn't really expect messages from the server when it's idle...

Re: Parameter status message not sent?

2018-02-13 Thread Craig Ringer
On 14 February 2018 at 10:26, Andres Freund wrote: > On 2018-02-14 11:12:30 +0900, Tatsuo Ishii wrote: > > According to the manual, backend sends a parameter status message when > > certain configuration variable has been changed and SIGHUP signal is > sent. > >

Re: Parameter status message not sent?

2018-02-13 Thread Andres Freund
On 2018-02-14 11:12:30 +0900, Tatsuo Ishii wrote: > According to the manual, backend sends a parameter status message when > certain configuration variable has been changed and SIGHUP signal is sent. > https://www.postgresql.org/docs/10/static/protocol-flow.html#PROTOCOL-ASYNC > >