From: Vivek Khera <khera@kcilink.com>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Wed, 22 Oct 2003 14:46:26 -0400
Message-ID: <x78yndcdq5.fsf@yertle.int.kciLink.com> (raw)
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<3F9006BF.40906@persistent.co.in>
<16272.4154.489000.227676@gargle.gargle.HOWL>
<cm90pvsbml6qdpe9el3qm66ogj7cpdk5ar@email.aon.at>
<16272.30527.120343.547492@jump.bivio.com>
>>>>> "RN" == Rob Nagler <nagler@bivio.biz> writes:
RN> This solution doesn't really fix the fact that VACUUM consumes the
RN> disk while it is running. I want to avoid the erratic performance on
RN> my web server when VACUUM is running.
What's the disk utilization proir to running vacuum? If it is
hovering around 95% or more of capacity, of course you're gonna
overwhelm it.
This ain't Star Trek -- the engines can't run at 110%, Cap'n!
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: khera@kcilink.com
Subject: Re: vacuum locking
In-Reply-To: <x78yndcdq5.fsf@yertle.int.kciLink.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox