Re: Patch to implement pg_current_logfile() function
От | Karl O. Pinc |
---|---|
Тема | Re: Patch to implement pg_current_logfile() function |
Дата | |
Msg-id | 20161027121141.6bd95efd@slate.meme.com обсуждение исходный текст |
Ответ на | Re: Patch to implement pg_current_logfile() function (Gilles Darold <gilles.darold@dalibo.com>) |
Ответы |
Re: Patch to implement pg_current_logfile() function
|
Список | pgsql-hackers |
On Thu, 27 Oct 2016 19:03:11 +0200 Gilles Darold <gilles.darold@dalibo.com> wrote: > >> Re: Karl O. Pinc 2016-10-27 > >> <20161026222513.74cd3def@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 <kop@meme.com> Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein
В списке pgsql-hackers по дате отправления: