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 4428A52E81 for ; Tue, 2 Aug 2005 14:08:22 -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 55673-02 for ; Tue, 2 Aug 2005 17:08:11 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 26FDB52E84 for ; Tue, 2 Aug 2005 14:08:10 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j72H89xv011915; Tue, 2 Aug 2005 13:08:09 -0400 (EDT) To: Christopher Browne Cc: pgsql-admin@postgresql.org Subject: Re: some databases have not been vacuumed ... In-reply-to: References: <42EE798A.5040305@lexum.umontreal.ca> <42EE7BA7.6030005@commandprompt.com> Comments: In-reply-to Christopher Browne message dated "Tue, 02 Aug 2005 10:28:52 -0400" Date: Tue, 02 Aug 2005 13:08:09 -0400 Message-ID: <11914.1123002489@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200508/20 X-Sequence-Number: 18339 Christopher Browne writes: > 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's not really necessary to guess about which database(s) are triggering the message: a quick look in pg_database will tell you. See TFM: http://www.postgresql.org/docs/8.0/static/maintenance.html#VACUUM-FOR-WRAPAROUND regards, tom lane