On 04/07/2016 10:06 AM, Alex Ignatov wrote:
>
>
> On 07.04.2016 17:59, Rob Sargent wrote:
>>
>>> On Apr 7, 2016, at 8:26 AM, Alex Ignatov <a.ignatov@postgrespro.ru>
>>> wrote:
>>>
>>>
>>>
>>>> On 07.04.2016 16:53, Tom Lane wrote:
>>>> Alex Ignatov <a.ignatov@postgrespro.ru> writes:
>>>>> My question is: is there any option(s) to log non-default
>>>>> postgresql.conf values to log file?
>>>> No, but you can easily find all the non-default settings by querying
>>>> the pg_settings view.
>>>>
>>>> regards, tom lane
>>> Yeah, i know it but pg_settings is available only after pg is ready
>>> to accept client connections.
>>> Also in some cases log file is placed on another server say, syslog.
>>> And if your pg server is not available you cant say anything about
>>> your pg_settings.
>> At that point you're looking in a file: log file or config file. Does
>> it matter which?
>>> --
>>> Alex Ignatov
>>> Postgres Professional: http://www.postgrespro.com
>>> The Russian Postgres Company
>>>
>>>
>>>
>>> --
>>> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-general
>>
> It matter when your pg host is down and all you have is log file. It is
> very usual situation. You need historical info.
So you are logging to another computer, otherwise if the host is down
how are you getting the log?
In any case Postgres does log changes to parameters in its log file:
-2016-04-07 10:39:21.868 PDT-0LOG: received SIGHUP, reloading
configuration files
-2016-04-07 10:39:21.869 PDT-0LOG: parameter "log_statement" changed to
"all"
-2016-04-07 10:44:42.930 PDT-0LOG: received SIGHUP, reloading
configuration files
-2016-04-07 12:44:42.989 CDT-0LOG: parameter "log_timezone" changed to
"US/Central
-2016-04-07 12:45:29.966 CDT-0LOG: parameter "log_statement" changed to
"mod"
-2016-04-07 10:45:29.966 PDT-0LOG: parameter "log_timezone" changed to
"US/Pacific"
>
--
Adrian Klaver
adrian.klaver@aklaver.com