Re: [HACKERS] Patch to implement pg_current_logfile() function - Mailing list pgsql-hackers

From Karl O. Pinc
Subject Re: [HACKERS] Patch to implement pg_current_logfile() function
Date
Msg-id 20170117080149.5d45bb02@slate.meme.com
Whole thread Raw
In response to Re: [HACKERS] Patch to implement pg_current_logfile() function  ("Karl O. Pinc" <kop@meme.com>)
List pgsql-hackers
On Tue, 17 Jan 2017 07:58:43 -0600
"Karl O. Pinc" <kop@meme.com> wrote:

> On Tue, 17 Jan 2017 11:22:45 +0900
> Michael Paquier <michael.paquier@gmail.com> wrote:
> 
> > On Tue, Jan 17, 2017 at 2:21 AM, Karl O. Pinc <kop@meme.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@meme.com>
Free Software:  "You don't pay back, you pay forward."                -- Robert A. Heinlein



pgsql-hackers by date:

Previous
From: "Karl O. Pinc"
Date:
Subject: Re: [HACKERS] Patch to implement pg_current_logfile() function
Next
From: Merlin Moncure
Date:
Subject: Re: [HACKERS] New CORRESPONDING clause design