X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6ED73D1B4ED for ; Sun, 5 Oct 2003 11:15:27 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 99929-10 for ; Sun, 5 Oct 2003 08:14:41 -0300 (ADT) Received: from wight.ymogen.net (unknown [217.27.240.153]) by svr1.postgresql.org (Postfix) with SMTP id 72566D1B540 for ; Sun, 5 Oct 2003 08:14:37 -0300 (ADT) Received: (qmail 26069 invoked from network); 5 Oct 2003 11:14:24 -0000 Received: from dsl-217-155-239-51.zen.co.uk (HELO finisterre) (217.155.239.51) by wight.ymogen.net with SMTP; 5 Oct 2003 11:14:24 -0000 From: "Matt Clark" To: "Andrew Sullivan" , Subject: Re: reindex/vacuum locking/performance? Date: Sun, 5 Oct 2003 12:14:24 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20031004152241.GL580@libertyrms.info> Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/152 X-Sequence-Number: 3900 > 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. Very true, which is why all my scripts write a lockfile and delete it when they're finished, to prevent that happening. I should have mentioned that. > 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. That's _very_ interesting. I've never been quite clear what's in shared buffers apart from scratch space for currently running transactions. Also the docs imply that vacuum uses it's own space for working in. Do you have more info on how it clobbers shared_buffers? M