odd output of pg_basebackup

On Mon, Feb 7, 2011 at 13:43, Fujii Masao <masao.fujii@gmail.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..

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

On Sun, Feb 13, 2011 at 17:44, Magnus Hagander <magnus@hagander.net> wrote:

On Mon, Feb 7, 2011 at 13:43, Fujii Masao <masao.fujii@gmail.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
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/