X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 53D5C52C74 for ; Mon, 1 Aug 2005 17:59:40 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 53154-04 for ; Mon, 1 Aug 2005 20:59:35 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id D6ABE52C00 for ; Mon, 1 Aug 2005 17:59:33 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 01 Aug 2005 15:59:35 -0500 Subject: Re: some databases have not been vacuumed ... From: Scott Marlowe To: FM Cc: Mailing List Postgres-Admin In-Reply-To: <42EE8B66.7080709@lexum.umontreal.ca> References: <42EE798A.5040305@lexum.umontreal.ca> <42EE7BA7.6030005@commandprompt.com> <42EE8B66.7080709@lexum.umontreal.ca> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1122929975.9182.49.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 01 Aug 2005 15:59:35 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200508/12 X-Sequence-Number: 18331 No. Vacuum full should not be necessary on a properly configured server. See: http://www.postgresql.org/docs/8.0/static/maintenance.html On Mon, 2005-08-01 at 15:51, FM wrote: > I vacumm all DB ...except... postgres ones. > > I"ll do a vacuum -all tonight > > What is you vacuum strategy ? > vacuum everyday and vacuum full analyse ervery week ? > > thanks ! > > > Joshua D. Drake wrote: > > FM wrote: > > > >> Hello after a vacuum full analyse I received this : > >> WARNING: some databases have not been vacuumed in 1805294030 > >> transactions > >> HINT: Better vacuum them within 342189617 transactions, or you may > >> have a wraparound failure. > >> > >> I read that it's because i do not vacuum DB very often. > >> Now I vacuum every night but the warning remains. > >> How can I get rid of this ? > > > > > > Run a vacuum full on all the database. > > > >> > >> Thanks ! > >> > >> ---------------------------(end of broadcast)--------------------------- > >> TIP 3: Have you checked our extensive FAQ? > >> > >> http://www.postgresql.org/docs/faq > > > > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster