From: Andrew Sullivan <andrew@libertyrms.info>
To: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: reindex/vacuum locking/performance?
Date: Sun, 5 Oct 2003 22:01:03 -0400
Message-ID: <20031006020103.GD3441@libertyrms.info> (raw)
In-Reply-To: <1065396767.466.12.camel@tokyo>
References: <60d6de9fah.fsf@dev6.int.libertyrms.info>
<LFEIJBEOKGPDHCEMDGNFAEOCCFAA.matt@ymogen.net>
<20031004152241.GL580@libertyrms.info>
<1065396767.466.12.camel@tokyo>
On Sun, Oct 05, 2003 at 07:32:47PM -0400, Neil Conway wrote:
> 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.
Hey, when that happens, you'll find me first in line to praise the
implementor; but until then, it's important that people not get the
idea that vacuum is free.
It is _way_ imporved, and on moderately loaded boxes, it'salmost
unnoticable. But under heavy load, you need to be _real_ careful
about calling vacuum. I think one of the biggest needs in the AVD is
some sort of intelligence about current load on the postmaster, but I
haven't the foggiest idea how to give it such intelligence.
A
--
----
Andrew Sullivan 204-4141 Yonge Street
Afilias Canada Toronto, Ontario Canada
<andrew@libertyrms.info> M2P 2A8
+1 416 646 3304 x110
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: andrew@libertyrms.info
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <20031006020103.GD3441@libertyrms.info>
* 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