| 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-02-13 16:44:10 |
| Message-ID: | AANLkTikv7Wg5WixPJG21Dm=pBNukHePrFTb7rBz5omwC@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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..
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-02-13 17:40:37 | Re: Extensions vs PGXS' MODULE_PATHNAME handling |
| Previous Message | Michael Banck | 2011-02-13 16:42:50 | Re: Debian readline/libedit breakage |