From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru> |
Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Non-default postgresql.conf values to log |
Date: | 2016-04-07 17:39:39 |
Message-ID: | CAKFQuwYu3VrxdaUyXqHgji=3k_OwqtQB+TmTxX8EYfuZ+4xBSw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 7, 2016 at 10:37 AM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Thu, Apr 7, 2016 at 10:06 AM, Alex Ignatov <a(dot)ignatov(at)postgrespro(dot)ru>
> 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 have the capability? I'd
> imagine it would default to OFF and/or would only happen when/if the
> database couldn't start successfully.
>
>
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.
I'm not sure how much merit "historical info" has and how one would
configure the server to ensure that said info is available when/if
eventually needed.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-04-07 17:46:05 | Re: Non-default postgresql.conf values to log |
Previous Message | David G. Johnston | 2016-04-07 17:37:55 | Re: Non-default postgresql.conf values to log |