| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to implement pg_current_logfile() function |
| Date: | 2017-01-20 01:19:06 |
| Message-ID: | CAB7nPqTe=aWQTJHmYco0L3Gz8rjWosSVjRT4oGd_7DHTOP=xbg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 20, 2017 at 12:08 AM, Karl O. Pinc <kop(at)meme(dot)com> wrote:
> Is this an argument for having the current_logfiles always exist
> and be empty when there is no in-filesystem logfile? It always felt
> to me that the code would be simpler that way.
Well, you'll need to do something in any case if the logging_collector
is found disabled and the syslogger process is restarted. So just
removing it looked cleaner to me. I am not strongly attached to one
way of doing or the other though.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-01-20 01:29:46 | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
| Previous Message | Tom Lane | 2017-01-20 00:09:45 | Re: [JDBC] SEGFAULT in HEAD with replication |