On Thu, 27 Oct 2016 19:03:11 +0200
Gilles Darold <gilles.dar...@dalibo.com> wrote:
> >> Re: Karl O. Pinc 2016-10-27
> >> <20161026222513.74cd3...@slate.meme.com>
> > Your comment makes me wonder if pg_current_logfile(), without
> > arguments, should instead be "SHOW current_logfile;".
> -1, SHOW is used to display run-time parameters values
Another interface to consider might be a system catalog:
SELECT * from postgres.pg_current_logfile;
format | path
-------+-------------------
syslog | /some/where/log
cvslog | /some/where/log.csv
(2 rows)
Maybe good if the goal is "interactive use". Seems like
overkill to me, but thought I'd present the idea
anyway.
Karl <k...@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
