| From: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
|---|---|
| To: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> |
| Cc: | Christoph Berg <myon(at)debian(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to implement pg_current_logfile() function |
| Date: | 2016-10-27 17:11:41 |
| Message-ID: | 20161027121141.6bd95efd@slate.meme.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 27 Oct 2016 19:03:11 +0200
Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> wrote:
> >> Re: Karl O. Pinc 2016-10-27
> >> <20161026222513(dot)74cd3def(at)slate(dot)meme(dot)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 <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-10-27 17:17:07 | Re: pg_hba_file_settings view patch |
| Previous Message | Gilles Darold | 2016-10-27 17:03:11 | Re: Patch to implement pg_current_logfile() function |