Re: pg_dump & performance degradation

At 01:49 1/08/00 -0500, Thomas Swan wrote:

>>>>

<excerpt>

All in all, hard coding in the delay, would aggravate me and quite a few
others; can't you hear it, "Why the *#!##(at)$ is this taking so long?"

</excerpt>

<<<<<<<<

Just in case there is a misunderstanding, this was never, ever, part of
the plan or implementation. The 'throttle' code was driven by a command
option...

>>>>

----------------------------------------------------------------

Philip Warner | __---_____

Albatross Consulting Pty. Ltd. |----/ - \

(A.C.N. 008 659 498) | /(@) ______---_

Tel: (+61) 0500 83 82 81 | _________ \

Fax: (+61) 0500 83 82 82 | ___________ |

Http://www.rhyme.com.au | / \|

| --________--

PGP key available upon request, | /

and from pgp5.ai.mit.edu:11371 |/