From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rob Nagler <nagler@bivio.biz>
Cc: pgsql-performance@postgresql.org
Subject: Re: vacuum locking
Date: Thu, 30 Oct 2003 12:28:47 -0500
Message-ID: <1113.1067534927@sss.pgh.pa.us> (raw)
In-Reply-To: <16289.14916.51000.772555@gargle.gargle.HOWL>
References: <16272.318.870000.93584@gargle.gargle.HOWL>
<87d6ciy3bf.fsf@stark.dyndns.tv>
<16288.19970.172547.319577@jump.bivio.com>
<200310291655.07363.josh@agliodbs.com>
<16289.14916.51000.772555@gargle.gargle.HOWL>
Rob Nagler <nagler@bivio.biz> writes:
> When vacuum is running, it's going through the entire
> database, and that pretty much trashes all other queries, especially
> DSS queries. As always it is just software, and there's got to be
> 80/20 solution.
One thing that's been discussed but not yet tried is putting a tunable
delay into VACUUM's per-page loop (ie, sleep N milliseconds after each
heap page is processed, and probably each index page too). This might
be useless or it might be the 80/20 solution you want. Want to try it
and report back?
regards, tom lane
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: tgl@sss.pgh.pa.us, nagler@bivio.biz
Subject: Re: vacuum locking
In-Reply-To: <1113.1067534927@sss.pgh.pa.us>
* 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