Re: Backup throttling

From: Boszormenyi Zoltan <zb(at)cybertec(dot)at>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Antonin Houska <antonin(dot)houska(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Backup throttling
Date: 2013-08-19 18:15:51
Message-ID: 521260D7.4080401@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2013-08-19 19:20 keltezéssel, Andres Freund írta:
> Hi,
>
> On 2013-07-24 09:20:52 +0200, Antonin Houska wrote:
>> Hello,
>> the purpose of this patch is to limit impact of pg_backup on running server.
>> Feedback is appreciated.
> Based on a quick look it seems like you're throttling on the receiving
> side. Is that a good idea? Especially over longer latency links, TCP
> buffering will reduce the effect on the sender side considerably.
>
> Greetings,
>
> Andres Freund

Throttling on the sender side requires extending the syntax of
BASE_BACKUP and maybe START_REPLICATION so both can be
throttled but throttling is still initiated by the receiver side.

Maybe throttling the walsender is not a good idea, it can lead
to DoS via disk space shortage.

Best regards,
Zoltán Böszörményi

--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de
http://www.postgresql.at/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Boszormenyi Zoltan 2013-08-19 18:19:14 Re: UNNEST with multiple args, and TABLE with multiple funcs
Previous Message Tom Lane 2013-08-19 18:13:50 Re: danger of stats_temp_directory = /dev/shm