From: Rob Nagler <nagler@bivio.biz>
To: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Fri, 17 Oct 2003 17:37:16 -0600
Message-ID: <16272.32044.80671.948532@jump.bivio.com> (raw)
In-Reply-To: <200310170936.25997.josh@agliodbs.com>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<3F9006BF.40906@persistent.co.in>
<16272.4154.489000.227676@gargle.gargle.HOWL>
<200310170936.25997.josh@agliodbs.com>
Josh Berkus writes:
> Yes, but it will have less of an impact on the system while it's running.
We'll find out. I lowered it to vacuum_mem to 32000.
> What sort of disk array do you have? That seems like a lot of time
> considering how little work VACUUM is doing.
Vendor: DELL Model: PERCRAID Mirror Rev: V1.0
Type: Direct-Access ANSI SCSI revision: 02
Two 10K disks attached.
Rob
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: nagler@bivio.biz
Subject: Re: vacuum locking
In-Reply-To: <16272.32044.80671.948532@jump.bivio.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