From: Neil Conway <neilc@samurai.com>
To: Andrew Sullivan <andrew@libertyrms.info>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: reindex/vacuum locking/performance?
Date: Sun, 05 Oct 2003 19:32:47 -0400
Message-ID: <1065396767.466.12.camel@tokyo> (raw)
In-Reply-To: <20031004152241.GL580@libertyrms.info>
References: <60d6de9fah.fsf@dev6.int.libertyrms.info>
<LFEIJBEOKGPDHCEMDGNFAEOCCFAA.matt@ymogen.net>
<20031004152241.GL580@libertyrms.info>
On Sat, 2003-10-04 at 11:22, Andrew Sullivan wrote:
> Also, a vacuum pretty much destroys your shared buffers, so you have
> to be aware of that trade-off too.
True, although there is no reason that this necessary needs to be the
case (at least, as far as the PostgreSQL shared buffer goes). As has
been pointed out numerous times on -hackers and in the literature, using
LRU for a DBMS shared buffer cache is far from optimal, and better
algorithms have been proposed (e.g. LRU-K, ARC). We could even have the
VACUUM command inform the bufmgr that the pages it is in the process of
reading in are part of a seqscan, and so are unlikely to be needed in
the immediate future.
-Neil
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: neilc@samurai.com, andrew@libertyrms.info
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <1065396767.466.12.camel@tokyo>
* 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