Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Tom Lane
"David G. Johnston" writes: > ​Admittedly, I'm not sure how you would fix any problems without access to > the server and its config files - at which point you are back to simply > reviewing those. Yeah. Other related problems include being unable to *find* the log file if you don't know what

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Adrian Klaver
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 wrote: On 07.04.2016 16:53, Tom Lane wrote: Alex Ignatov writes: My question is: is there any option(s) to log non-default postgresql.conf values to log file?

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread David G. Johnston
On Thu, Apr 7, 2016 at 10:37 AM, David G. Johnston < david.g.johns...@gmail.com> wrote: > On Thu, Apr 7, 2016 at 10:06 AM, Alex Ignatov > wrote: > >> It matter when your pg host is down and all you have is log file. It is >> very usual situation. You need historical info. > > > ​I think this woul

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread David G. Johnston
On Thu, Apr 7, 2016 at 10:06 AM, Alex Ignatov wrote: > It matter when your pg host is down and all you have is log file. It is > very usual situation. You need historical info. ​I think this would be a good idea. Is it something you are thinking of writing now that you see PostgreSQL does not

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Alex Ignatov
On 07.04.2016 17:59, Rob Sargent wrote: On Apr 7, 2016, at 8:26 AM, Alex Ignatov wrote: On 07.04.2016 16:53, Tom Lane wrote: Alex Ignatov 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-defau

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Rob Sargent
> On Apr 7, 2016, at 8:26 AM, Alex Ignatov wrote: > > > >> On 07.04.2016 16:53, Tom Lane wrote: >> Alex Ignatov 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 queryin

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Alex Ignatov
On 07.04.2016 16:53, Tom Lane wrote: Alex Ignatov 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

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Tom Lane
Alex Ignatov 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 -- Sent via pgsql-general mailing list (

Re: [GENERAL] Non-default postgresql.conf values to log

2016-04-07 Thread Christoph Moench-Tegeder
## Alex Ignatov (a.igna...@postgrespro.ru): > My question is: is there any option(s) to log non-default > postgresql.conf values to log file? Depending on your use case, I'd start with a simple query: SELECT name, setting FROM pg_settings WHERE source <> 'default' Wrap that in a COPY, or perhaps