Postgres Pro
Downloads
Home   >   mailing lists

Re: Patch to implement pg_current_logfile() function - Mailing list pgsql-hackers

From Shulgin, Oleksandr
Subject Re: Patch to implement pg_current_logfile() function
Date
Msg-id CACACo5QHXucrYOcf_xMo9=kGkuhx=XSURnahO0vzEKGBhJCPnQ@mail.gmail.com
Whole thread Raw
In response to Re: Patch to implement pg_current_logfile() function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Patch to implement pg_current_logfile() function
List pgsql-hackers
Tree view
On Thu, Mar 10, 2016 at 9:05 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Gilles Darold <gilles.darold@dalibo.com> writes:
> Then, should I have to use an alternate file to store the information or
> implement a bidirectional communication with the syslogger?

I'd just define a new single-purpose file $PGDATA/log_file_name
or some such.

Would it make sense to have it as a symlink instead?

--
Alex

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Improving replay of XLOG_BTREE_VACUUM records
Next
From: Mithun Cy
Date:
Subject: Re: Explain [Analyze] produces parallel scan for select Into table statements.