From: Andrew Sullivan <andrew@libertyrms.info>
To: pgsql-performance@postgresql.org
Subject: Re: reindex/vacuum locking/performance?
Date: Sat, 4 Oct 2003 11:22:41 -0400
Message-ID: <20031004152241.GL580@libertyrms.info> (raw)
In-Reply-To: <LFEIJBEOKGPDHCEMDGNFAEOCCFAA.matt@ymogen.net>
References: <60d6de9fah.fsf@dev6.int.libertyrms.info>
<LFEIJBEOKGPDHCEMDGNFAEOCCFAA.matt@ymogen.net>
On Sat, Oct 04, 2003 at 12:29:55AM +0100, Matt Clark wrote:
> My real world experience on a *very* heavily updated OLTP type DB, following
> advice from this list (thanks guys!), is that there is essentially zero cost
> to going ahead and vacuuming as often as you feel like it. Go crazy, and
> speed up your DB!
That's not quite true. If vacuums start running into each other, you
can very easily start eating up all your I/O bandwidth. Even if you
gots lots of it.
Also, a vacuum pretty much destroys your shared buffers, so you have
to be aware of that trade-off too. Vacuum is not free. It's _way_
cheaper than it used to be, though.
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: <20031004152241.GL580@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