Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 681B79FB4DE for ; Tue, 17 Apr 2007 04:54:11 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 75788-01 for ; Tue, 17 Apr 2007 04:54:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from vesuvio.facultas.co.uk (lvps212-241-196-224.vps.webfusion.co.uk [212.241.196.224]) by postgresql.org (Postfix) with ESMTP id 21D0C9FB313 for ; Tue, 17 Apr 2007 04:54:06 -0300 (ADT) Received: (qmail 29779 invoked from network); 17 Apr 2007 07:54:05 +0000 Received: from office.lyris.co.uk (HELO KieranX15) (195.137.95.103) by lvps212-241-196-224.vps.webfusion.co.uk with SMTP; 17 Apr 2007 07:54:05 +0000 Message-ID: <00ed01c780c5$91dd2390$0b02a8c0@KieranX15> From: "Kieran Cooper, Lyris UK" To: "Matthew T. O'Connor" Cc: References: <001901c78071$9a9a1f00$0b02a8c0@KieranX15> <4623F54E.3030900@zeut.net> Subject: Re: Vacuum stops with misleading max_fsm_pages error Date: Tue, 17 Apr 2007 08:51:46 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/147 X-Sequence-Number: 25211 > Kieran Cooper, Lyris UK wrote: >> We're managing a database on version 8.2.3 (running Lyris ListManager >> email software). I ran a 'vacuum analyze full verbose' (we haven't been >> able to get autovacuum to work properly on Lyris installs so we need to >> run a full vacuum every week or so, and we'd been doing some work on this >> machine so it needed it). It ran happily for quite a while - about 2 >> thirds of the way through the database - but then ended with the lines > > > What is it about autovacuum that isn't working for you? Hi Matthew. I have to admit that I haven't tested full yet, but here's the scenario: When Lyris sends a mailing there is an intense amount of database activity - particularly on two tables. When I had auto vacuum set up, the database just wasn't responding fast enough, so the mailing speed dropped as Lyris dynamically adjusted based on the speed of db response. I guess what I need to do is tweak the intervals and the sleep time so that vacuum backs off when the database is really busy - do you have any thoughts on what settings I should try in order to acheive that? Thanks so much Kieran