Re: pg_dump & performance degradation

From: Thomas Swan <tswan(at)olemiss(dot)edu>
To: Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump & performance degradation
Date: 2000-08-01 07:48:32
Message-ID: 4.3.2.7.2.20000801024801.01de43b8@sunset.backbone.olemiss.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


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

Browse pgsql-general by date

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

Browse pgsql-hackers by date

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