X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id A9B399DC997
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 25 Jan 2006 12:24:36 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 11054-09
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Wed, 25 Jan 2006 12:24:34 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by postgresql.org (Postfix) with ESMTP id 4A4989DC8A9
	for <pgsql-performance@postgresql.org>;
	Wed, 25 Jan 2006 12:24:33 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0PGLwa5001460;
	Wed, 25 Jan 2006 11:21:58 -0500 (EST)
To: Richard Huxton <dev@archonet.com>
cc: Evgeny Gridasov <eugrid@fpm.kubsu.ru>, pgsql-performance@postgresql.org
Subject: Re: DB responce during DB dump 
In-reply-to: <43D772BD.8080809@archonet.com> 
References: <GJEAKHIALCNFPPGBGEKNEEBDDGAA.dan@centrifugesolutions.com>
	<20060125150134.55589806.eugrid@fpm.kubsu.ru>
	<43D772BD.8080809@archonet.com>
Comments: In-reply-to Richard Huxton <dev@archonet.com>
	message dated "Wed, 25 Jan 2006 12:44:45 +0000"
Date: Wed, 25 Jan 2006 11:21:58 -0500
Message-ID: <1459.1138206118@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0.098 required=5 tests=[AWL=0.098]
X-Spam-Score: 0.098
X-Spam-Level: 
X-Archive-Number: 200601/431
X-Sequence-Number: 16909

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