On Thu, 2010-06-17 at 13:33 -0400, Tom Lane wrote:
> Fujii Masao writes:
> > On Wed, Jun 16, 2010 at 12:24 PM, Takahiro Itagaki
> > 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 pa
Fujii Masao writes:
> On Wed, Jun 16, 2010 at 12:24 PM, Takahiro Itagaki
> 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.
>> N
On Wed, Jun 16, 2010 at 12:24 PM, Takahiro Itagaki
wrote:
>
> Fujii Masao wrote:
>
>> This is because pg_archivecleanup puts the line break "\n" in the head of
>> debug message. Why should we do so?
>>
>> ---
>> if (debug)
>> fprintf(stderr, "\n%s: removing \"%s\"", prog
Fujii Masao wrote:
> This is because pg_archivecleanup puts the line break "\n" in the head of
> debug message. Why should we do so?
>
> ---
> if (debug)
> fprintf(stderr, "\n%s: removing \"%s\"", progname, WALFilePath);
> ---
We also need "\n" at
Hi,
Sometimes the postgres server log message and the pg_archivecleanup debug
message are output in the same line as follows. This is a little hard to
read.
---
LOG: restored log file "0001006B" from archive
pg_archivecleanup: keep WAL file 000100
