From: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Non-default postgresql.conf values to log |
Date: | 2016-04-07 17:06:48 |
Message-ID: | 570693A8.4040707@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07.04.2016 17:59, Rob Sargent wrote:
>
>> On Apr 7, 2016, at 8:26 AM, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> wrote:
>>
>>
>>
>>> On 07.04.2016 16:53, Tom Lane wrote:
>>> Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)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(at)postgresql(dot)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.
--
Alex Ignatov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2016-04-07 17:35:30 | Re: what database schema version management system to use? |
Previous Message | Alvaro Herrera | 2016-04-07 16:31:48 | Re: 9.5 new features |