Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id A4E609FA46C for ; Tue, 17 Apr 2007 04:36:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 39734-09 for ; Tue, 17 Apr 2007 04:35:58 -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 4E21A9FA49B for ; Tue, 17 Apr 2007 04:36:00 -0300 (ADT) Received: (qmail 14237 invoked from network); 17 Apr 2007 07:35:58 +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:35:58 +0000 Message-ID: <00a801c780c3$0aad0e00$0b02a8c0@KieranX15> From: "Kieran Cooper, Lyris UK" To: "Joshua D. Drake" , "Tom Lane" Cc: References: <001901c78071$9a9a1f00$0b02a8c0@KieranX15> <4623F3F6.8040408@commandprompt.com> <11516.1176762986@sss.pgh.pa.us> Subject: Re: Vacuum stops with misleading max_fsm_pages error Date: Tue, 17 Apr 2007 08:35:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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/146 X-Sequence-Number: 25210 > "Joshua D. Drake" writes: >> Kieran Cooper, Lyris UK wrote: >>> INFO: free space map contains 20914 pages in 61 relations >>> DETAIL: A total of 14992 page slots are in use (including overhead). >>> 14992 page slots are required to track all free space. >>> Current limits are: 900000 page slots, 6000 relations, using 5659 kB. > >> I am not sure what your question is. The above looks perfectly >> reasonable. > I think he's wondering why the second number is less than the first. > AFAICT that should be impossible after a VACUUM FULL, but there are > probably tables that haven't been touched by the VACUUM FULL --- stuff > in other databases being one obvious possibility. As for the vacuum > not having done every table in the current database, did you run it > as superuser? > > regards, tom lane Thanks for your messages Tom and Josh. The problem I'm finding is that the Vacuum finishes before it has touched all the tables in the database. When I run it on the same database in the same way on other servers, it does all the tables. There is only 1 database on this machine (in addition to template1 and template2). I'm running it from within the postgres command line, logged in as postgres. Thanks Kieran