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 3EAF952C8C for ; Tue, 2 Aug 2005 12:12:26 -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 23928-07 for ; Tue, 2 Aug 2005 15:12:15 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id DBF1A52C6D for ; Tue, 2 Aug 2005 12:12:15 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j72FCFDX028971 for ; Tue, 2 Aug 2005 15:12:15 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j72EtJIW024975 for pgsql-admin@postgresql.org; Tue, 2 Aug 2005 14:55:19 GMT (envelope-from news) From: Christopher Browne X-Newsgroups: pgsql.admin Subject: Re: some databases have not been vacuumed ... Date: Tue, 02 Aug 2005 10:28:52 -0400 Organization: cbbrowne Computing Inc Lines: 30 Message-ID: References: <42EE798A.5040305@lexum.umontreal.ca> <42EE7BA7.6030005@commandprompt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:UqpeT3E5PnuUgye0gbTGPoqfXHg= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200508/19 X-Sequence-Number: 18338 In an attempt to throw the authorities off his trail, jd@commandprompt.com ("Joshua D. Drake") transmitted: > 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. That seems overkill. The problem is likely that the "old tuples" are in some database not being vacuumed. template1 is a likely candidate; do a plain VACUUM on that and the message may go away. It can be *possible* for the issue to be with template0, if it had at some point been open for modification. If that is the case, it is a good idea to: - Unlock template0 (via table pg_database) - Run VACUUM FREEZE on template0 - Relock it -- (format nil "~S@~S" "cbbrowne" "gmail.com") http://linuxdatabases.info/info/slony.html "You think you know when you can learn, are more sure when you can write, even more when you can teach, but certain when you can program." -- Alan Perlis