Re: debug log in pg_archivecleanup - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: debug log in pg_archivecleanup
Date
Msg-id 1276851076.23257.81482.camel@ebony
Whole thread Raw
In response to Re: debug log in pg_archivecleanup  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2010-06-17 at 13:33 -0400, Tom Lane wrote:
> Fujii Masao <masao.fujii@gmail.com> writes:
> > On Wed, Jun 16, 2010 at 12:24 PM, Takahiro Itagaki
> > <itagaki.takahiro@oss.ntt.co.jp> wrote:
> >> This is because pg_archivecleanup puts the line break "\n" in the head of
> >> debug message. Why should we do so?
> 
> > Yes. What about the attached patch?
> 
> Applied along with a bit of further editorialization.
> 
> >> Note that we don't need a line break at Line 130
> >> because strerror() fills the last %s.
> >> L.130: fprintf(stderr, "\n%s: ERROR failed to remove \"%s\": %s",
> 
> > Right.
> 
> Huh?  strerror() doesn't include a newline.

Thanks.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Debug message in RemoveOldXlogFiles
Next
From: Thom Brown
Date:
Subject: Re: pg_dump does not honor namespaces when functions are used in index