From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Huxton <dev@archonet.com>
Cc: Evgeny Gridasov <eugrid@fpm.kubsu.ru>
Cc: pgsql-performance@postgresql.org
Subject: Re: DB responce during DB dump
Date: Wed, 25 Jan 2006 11:21:58 -0500
Message-ID: <1459.1138206118@sss.pgh.pa.us> (raw)
In-Reply-To: <43D772BD.8080809@archonet.com>
References: <GJEAKHIALCNFPPGBGEKNEEBDDGAA.dan@centrifugesolutions.com>
<20060125150134.55589806.eugrid@fpm.kubsu.ru>
<43D772BD.8080809@archonet.com>
Richard Huxton <dev@archonet.com> writes:
> Evgeny Gridasov wrote:
>> I've written a perl script to limit pg_dump output bandwidth,
>> ...
>> Is there any other solution to avoid this problem?
> That's an interesting solution, and I'd guess people might like to see
> it posted to the list if it's not too big.
Years ago there was some experimentation with dump-rate throttling logic
inside pg_dump itself --- there's still a comment about it in pg_dump.c.
The experiment didn't seem very successful, which is why it never got to
be a permanent feature. I'm curious to know why this perl script is
doing a better job than we were able to do inside pg_dump.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, dev@archonet.com, eugrid@fpm.kubsu.ru
Subject: Re: DB responce during DB dump
In-Reply-To: <1459.1138206118@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox