Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 550761337B6C for ; Fri, 21 Jan 2011 18:32:29 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 18149-05 for ; Fri, 21 Jan 2011 22:32:21 +0000 (UTC) X-Greylist: delayed 00:43:52.072144 by SQLgrey-1.7.6 Received: from mail.kickstone.com (smtp.kickstone.co.uk [87.194.183.70]) by mail.postgresql.org (Postfix) with ESMTP id B0CE31337990 for ; Fri, 21 Jan 2011 18:32:21 -0400 (AST) Received: from 87-194-183-69.dsl.cnl.uk.net ([87.194.183.69]:2087 helo=MADRAS2) by mail.kickstone.com with esmtpa (Exim 4.71) (envelope-from ) id 1PgOqH-0002Oy-4q for pgsql-admin@postgresql.org; Fri, 21 Jan 2011 21:48:25 +0000 Message-ID: <927BF3A3F54247FF8C63219A00CE98B5@squarepi.com> From: "John Lister" To: Subject: Should autovacuum do a database wide vacuum near transaction limit? Date: Fri, 21 Jan 2011 21:48:24 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01CBB9B4.EE0BE580" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=-10 required=5 tests=BAYES_40=-0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 201101/141 X-Sequence-Number: 36581 This is a multi-part message in MIME format. ------=_NextPart_000_0006_01CBB9B4.EE0BE580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'm running 8.3.9 on ubuntu with autovacuum enabled and seemingly = working properly., however I've started getting messages saying that I'm = near the transaction limit and I need to do a database wide vacuum, = which I've started.