From: Andrew Sullivan <andrew@libertyrms.info>
To: pgsql-performance@postgresql.org
Subject: Re: reindex/vacuum locking/performance?
Date: Sun, 5 Oct 2003 10:34:31 -0400
Message-ID: <20031005143431.GC3441@libertyrms.info> (raw)
In-Reply-To: <LFEIJBEOKGPDHCEMDGNFOEPHCFAA.matt@ymogen.net>
References: <20031004152241.GL580@libertyrms.info>
<LFEIJBEOKGPDHCEMDGNFOEPHCFAA.matt@ymogen.net>
On Sun, Oct 05, 2003 at 12:14:24PM +0100, Matt Clark wrote:
> more info on how it clobbers shared_buffers?
Vacuum is like a seqscan. It touches everything on a table. So it
doesn't clobber them, but that's the latest data. It's unlikely your
buffers are big enough to hold your database, unless your database is
small. So you'll end up expiring potentially useful data in the
buffer.
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: <20031005143431.GC3441@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