Re: DB responce during DB dump

From: Evgeny Gridasov
Subject: Re: DB responce during DB dump
Date: ,
Msg-id: 20060125194309.8cb6e5c8.eugrid@fpm.kubsu.ru
(view: Whole thread, Raw)
In response to: Re: DB responce during DB dump  (Tom Lane)
List: pgsql-performance

Tree view

Inconsistant query plan  ("Daniel Gish", )
 Re: Inconsistant query plan  (Scott Marlowe, )
 Re: Inconsistant query plan  (Michael Fuhr, )
  Re: Inconsistant query plan  ("Daniel Gish", )
   Re: Inconsistant query plan  (Alessandro Baretta, )
 DB responce during DB dump  (Evgeny Gridasov, )
  Re: DB responce during DB dump  (Richard Huxton, )
   Re: DB responce during DB dump  (Tom Lane, )
    Re: DB responce during DB dump  (Evgeny Gridasov, )
   Re: DB responce during DB dump  (Evgeny Gridasov, )

All I was trying to achieve is to limit I/O rate done by pg_dump.
The script is a very simple pipe rate limitter and nothing more:
it reads input, but outputs data no more than at rate specified.

I guess it helps because even if pg_dump outputs data at 20 mb/sec,
the script won't be able to read it at rate higher than output rate. Pipe
buffer is not infinitive, so pg_dump output rate and hard disk reads become
almost equal the input rate of my perl script.

On Wed, 25 Jan 2006 11:21:58 -0500
Tom Lane <> wrote:

> 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.

--
Evgeny Gridasov
Software Engineer
I-Free, Russia


pgsql-performance by date:

From: Evgeny Gridasov
Date:
Subject: Re: DB responce during DB dump
From: Robert Lor
Date:
Subject: PostgreSQL Solaris packages now in beta