Re: reindex/vacuum locking/performance?

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: reindex/vacuum locking/performance?
Date: 2003-10-04 15:22:41
Message-ID: 20031004152241.GL580@libertyrms.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andrew Sullivan 2003-10-04 15:23:38 Re: reindex/vacuum locking/performance?
Previous Message Andrew Sullivan 2003-10-04 15:18:54 Re: reindex/vacuum locking/performance?