>>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?"
>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...
It was... my apologies...

Thomas

-
- Thomas Swan
- Graduate Student  - Computer Science
- The University of Mississippi
-
- "People can be categorized into two fundamental
- groups, those that divide people into two groups
- and those that don't."

In response to

• Re: pg_dump & performance degradation at 2000-08-01 06:54:49 from Philip Warner

pgsql-hackers by date

Next:	From: Trond Eivind=?iso-8859-1?q?_Glomsr=F8d?=	Date: 2000-08-01 11:57:25
	Subject: Re: RPMs built for Mandrake
Previous:	From: Philip Warner	Date: 2000-08-01 06:54:49
	Subject: Re: pg_dump & performance degradation

pgsql-general by date

Next:	From: luc00	Date: 2000-08-01 08:35:14
	Subject: Embedded SQL C++ preprocessor ?
Previous:	From: Philip Warner	Date: 2000-08-01 06:54:49
	Subject: Re: pg_dump & performance degradation