X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 6EDAFD8A56 for ; Sat, 3 Sep 2005 11:01:17 -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 57525-09 for ; Sat, 3 Sep 2005 14:01:14 +0000 (GMT) Received: from eastrmmtao06.cox.net (eastrmmtao06.cox.net [68.230.240.33]) by svr1.postgresql.org (Postfix) with ESMTP id 10E8FD77A4 for ; Sat, 3 Sep 2005 11:01:13 -0300 (ADT) Received: from [192.168.0.17] (really [24.250.197.37]) by eastrmmtao06.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050903140117.TPUC18478.eastrmmtao06.cox.net@[192.168.0.17]>; Sat, 3 Sep 2005 10:01:17 -0400 From: Robert Treat To: pgsql-admin@postgresql.org Subject: Re: VACUMM problem Date: Sat, 3 Sep 2005 10:01:16 -0400 User-Agent: KMail/1.6.2 Cc: Marek Dabrowski References: <4319A36B.1070205@infor.pl> In-Reply-To: <4319A36B.1070205@infor.pl> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Message-Id: <200509031001.17118.xzilla@users.sourceforge.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.008 required=5 tests=[AWL=0.008] X-Spam-Level: X-Archive-Number: 200509/21 X-Sequence-Number: 18758 On Saturday 03 September 2005 09:21, Marek Dabrowski wrote: > Hello > > I didn't do VACUUM long time and now I have problem: > > WARNING: some databases have not been vacuumed in over 2 billion > transactions > DETAIL: You may have already suffered transaction-wraparound data loss. > > What I have to do to resolve this problem? > I would recommend you go through each database in your cluster and run "vacuum verbose;" any tables that have a high number of unused tuples in the output (say more unused than used) should have vacuum full run on them. Also at the end of each vacuum run, it will tell you how many free pages you need... write this down and adjust your postgresql.conf accordingly. Finally I would suggest you set up an automated process to run vaccum for you, or enable autovacuum if it is available. The docs can help you with specifics on most of these items. -- Robert Treat Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL