From: Rod Taylor <pg@rbt.ca>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: marty@outputservices.com, herve@elma.fr, Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Sat, 22 Jan 2005 14:00:40 -0500
Message-ID: <1106420440.35299.763.camel@home> (raw)
In-Reply-To: <20050122184124.GA21889@wolff.to>
References: <41F144FE.30902@outputservices.com>
<41F14758.4030602@outputservices.com>
<20050122.121300.41631131.t-ishii@sra.co.jp>
<20050122184124.GA21889@wolff.to>
On Sat, 2005-01-22 at 12:41 -0600, Bruno Wolff III wrote:
> On Sat, Jan 22, 2005 at 12:13:00 +0900,
> Tatsuo Ishii <t-ishii@sra.co.jp> wrote:
> >
> > Probably VACUUM works well for small to medium size tables, but not
> > for huge ones. I'm considering about to implement "on the spot
> > salvaging dead tuples".
>
> You are probably vacuuming too often. You want to wait until a significant
> fraction of a large table is dead tuples before doing a vacuum. If you are
> scanning a large table and only marking a few tuples as deleted, you aren't
> getting much bang for your buck.
The big problem occurs when you have a small set of hot tuples within a
large table. In the time it takes to vacuum a table with 200M tuples
one can update a small subset of that table many many times.
Some special purpose vacuum which can target hot spots would be great,
but I've always assumed this would come in the form of table
partitioning and the ability to vacuum different partitions
independently of each-other.
--
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: pg@rbt.ca, bruno@wolff.to, t-ishii@sra.co.jp
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <1106420440.35299.763.camel@home>
* 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