From: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, 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: | 2017-01-17 14:01:49 |
Message-ID: | 20170117080149.5d45bb02@slate.meme.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 17 Jan 2017 07:58:43 -0600
"Karl O. Pinc" <kop(at)meme(dot)com> wrote:
> On Tue, 17 Jan 2017 11:22:45 +0900
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
> > On Tue, Jan 17, 2017 at 2:21 AM, Karl O. Pinc <kop(at)meme(dot)com>
> > wrote:
>
> > >>Also, I would rather see an ERROR returned to the user in case of
> > >>bad data in current_logfiles,
> >
> > Hm... OK. At the same time not throwing at least a WARNING is
> > confusing
What I find a little disconcerting is that there'd be nothing in the
logs.
Karl <kop(at)meme(dot)com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2017-01-17 14:20:25 | Re: New CORRESPONDING clause design |
Previous Message | Karl O. Pinc | 2017-01-17 13:58:43 | Re: Patch to implement pg_current_logfile() function |