Skip site navigation (1) Skip section navigation (2)

Re: odd output of pg_basebackup

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: odd output of pg_basebackup
Date: 2011-03-19 15:47:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Sun, Feb 13, 2011 at 17:44, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Mon, Feb 7, 2011 at 13:43, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> Hi,
>> When I ran pg_basebackup with -x, -P and -v options, I encountered
>> the following odd output.
>>    $ pg_basebackup -D hoge -x -P -v
>>    xlog start point: 0/2000020
>>    33708/17322 kB (100%) 1/1 tablespaces (
>>  )000002)
>> "000002)" is a part of the previously reported message, it looks
>> odd that the subsequent progress report doesn't reset that. We
>> should reset the output buffer with each progress report?
> Yes. I thought I had fixed that already.. Hmm. I'll stick it on my list..

I had fixed it, it was sitting in the patch with functionality for
streaming the xlog during base backup over a second connection istead
of in the main one.

Since it looks like I won't be able to finish that one in time, I have
extracted the fix for this problem from it and applied it as a
separate patch.

 Magnus Hagander

In response to

pgsql-hackers by date

Next:From: Magnus HaganderDate: 2011-03-19 16:02:15
Subject: Re: Indent authentication overloading
Previous:From: Grzegorz JaskiewiczDate: 2011-03-19 15:34:18
Subject: Re: sync rep & fsync=off

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group