| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | PostgreSQL - Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Antonin Houska <antonin(dot)houska(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Backup throttling |
| Date: | 2013-08-22 13:33:15 |
| Message-ID: | 5216131B.1020201@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/22/2013 01:39 PM, PostgreSQL - Hans-Jürgen Schönig wrote:
> what would be a reasonable scenario where limiting streaming would make sense? i cannot think of any to be honest.
I tend to agree. If anything we're likely to want the reverse - the
ability to throttle WAL *generation* on the master so streaming can keep up.
I see a lot of value in throttling base backup transfer rates. It's
something PgBarman does per-tablespace using rsync at the moment, but
it'd be nice if it available as an option possible over the streaming
replication protocol via pg_basebackup so it was easier for people to
use ad-hoc and without all the shell access wrangling.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2013-08-22 13:33:34 | Re: pg_system_identifier() |
| Previous Message | Jov | 2013-08-22 13:23:36 | Re: proposal: lob conversion functionality |