From: | Dmitry Markman <dmarkman(at)mac(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: how to find log |
Date: | 2020-12-21 18:08:35 |
Message-ID: | 66596D56-89DD-46EB-8C81-94AE904204B8@mac.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks Tom, Andrew
I’ll try out logging_collector facility
thanks again
dm
> On Dec 20, 2020, at 12:04 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> On 12/20/20 11:31 AM, Tom Lane wrote:
>> Dmitry Markman <dmarkman(at)mac(dot)com> writes:
>>> suppose I started the server with the following command
>>> pg_ctl -D . . . start -l <logfilename>
>>> is there a way to get <logfilename> later by sending some query to the server or
>> No, the server has no way to know where its stdout/stderr were
>> pointed to. You might want to enable the syslogger output method
>> (see logging_collector) to have something a bit more featureful.
>>
>> https://www.postgresql.org/docs/current/runtime-config-logging.html
>>
>>
>
>
>
> Alternatively, asking the OS in many cases will work, e.g. on my linux
> machine:
>
>
> ls -l /proc/{postmasterpid}/fd/1
>
>
> cheers
>
>
> andrew
>
> --
> Andrew Dunstan
> EDB: https://www.enterprisedb.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-12-21 18:15:37 | Re: Weird special case in jsonb_concat() |
Previous Message | Surafel Temesgen | 2020-12-21 18:01:23 | Re: WIP: System Versioned Temporal Table |