From: Bruno Wolff III <bruno@wolff.to>
To: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: marty@outputservices.com
Cc: herve@elma.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Sat, 22 Jan 2005 12:41:24 -0600
Message-ID: <20050122184124.GA21889@wolff.to> (raw)
In-Reply-To: <20050122.121300.41631131.t-ishii@sra.co.jp>
References: <41F144FE.30902@outputservices.com>
<41F14758.4030602@outputservices.com>
<20050122.121300.41631131.t-ishii@sra.co.jp>
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.
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: bruno@wolff.to, t-ishii@sra.co.jp, marty@outputservices.com, herve@elma.fr
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <20050122184124.GA21889@wolff.to>
* 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