Re: [PATCH] pg_basebackup: progress report max once per second

From: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
To: Mika Eloranta <mel(at)ohmu(dot)fi>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pg_basebackup: progress report max once per second
Date: 2013-11-18 05:53:20
Message-ID: CAD21AoAnaukeO8zyM5CqYc_tNR8x_9w6p1uTjMsBLEca6odw=A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 14, 2013 at 6:27 PM, Mika Eloranta <mel(at)ohmu(dot)fi> wrote:
> On 13 Nov 2013, at 20:51, Mika Eloranta <mel(at)ohmu(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2013-11-18 06:01:54 Re: Extra functionality to createuser
Previous Message Haribabu kommi 2013-11-18 05:49:15 Re: New option for pg_basebackup, to specify a different directory for pg_xlog