| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dmitry Markman <dmarkman(at)mac(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: how to find log |
| Date: | 2020-12-20 17:04:56 |
| Message-ID: | 81968551-27ed-d70b-76c9-ac7c17972948@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 | Andrew Dunstan | 2020-12-20 17:09:59 | Re: multi-install PostgresNode |
| Previous Message | Tom Lane | 2020-12-20 16:31:00 | Re: how to find log |