Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] pg_basebackup: progress report max once per second - Mailing list pgsql-hackers

From Sawada Masahiko
Subject Re: [PATCH] pg_basebackup: progress report max once per second
Date
Msg-id CAD21AoAnaukeO8zyM5CqYc_tNR8x_9w6p1uTjMsBLEca6odw=A@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] pg_basebackup: progress report max once per second  (Mika Eloranta <mel@ohmu.fi>)
Responses Re: [PATCH] pg_basebackup: progress report max once per second  (Oskari Saarenmaa <os@ohmu.fi>)
List pgsql-hackers
Tree view 
On Thu, Nov 14, 2013 at 6:27 PM, Mika Eloranta <mel@ohmu.fi> wrote:
> On 13 Nov 2013, at 20:51, Mika Eloranta <mel@ohmu.fi> wrote:
>
>> Prevent excessive progress reporting that can grow to gigabytes
>> of output with large databases.
>
> Same patch as an attachment.
>
> --
> Mika Eloranta
> Ohmu Ltd.  http://www.ohmu.fi/
>

I got error with following scenario.

$ initdb -D data -E UTF8 --no-locale
/* setting the replication parameters */
$ pg_basebackup -D 2data
Floating point exception
LOG:  could not send data to client: Broken pipe
ERROR:  base backup could not send data, aborting backup
FATAL:  connection to client lost


Regards,

-------
Sawada Masahiko

pgsql-hackers by date:

Previous
From: Haribabu kommi
Date:
Subject: Re: New option for pg_basebackup, to specify a different directory for pg_xlog
Next
From: Amit Kapila
Date:
Subject: Re: Extra functionality to createuser