Re: Parameter status message not sent?

> 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) check for any other interesting events that happened while we
> * slept.
> */
> if (ConfigReloadPending)
> {
> ConfigReloadPending = false;
> ProcessConfigFile(PGC_SIGHUP);
> }
>
> which'll then, in turn, send out ParameterStatus messages for changed
> GUC_REPORT GUCs.

Thanks. I confirmed what you said by using strace attached to
backend.

One thing I noticed was, some GUC variables were sent as well even if
they were not changed.

sendto(10, "S\0\0\0\27DateStyle\0ISO, MDY\0S\0\0\0\23TimeZone\0Japan\0S\0\0\0#standard_conforming_strings\0on\0T\0\0\0!\0\1?column?\0\0\0\0\0\0\0\0\0\0\27\0\4\377\377\377\377\0\0D\0\0\0\v\0\1\0\0\0\0011C\0\0\0\rSELECT 1\0Z\0\0\0\5I", 146, 0, NULL, 0) = 146

So not only standard_conforming_strings, but Datestyle and TimeZone
were sent to frontend (I only changed standard_conforming_strings in
postgresql.conf).

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp