Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id A18E32E0202 for ; Sun, 16 Dec 2007 16:22:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 75629-10 for ; Sun, 16 Dec 2007 16:22:29 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 4DE9B2E01DD for ; Sun, 16 Dec 2007 16:22:32 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.1/8.14.1) with ESMTP id lBGKMTwc085333 for ; Sun, 16 Dec 2007 16:22:29 -0400 (AST) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.1/8.14.1/Submit) id lBGK82ZJ065468 for pgsql-admin@postgresql.org; Sun, 16 Dec 2007 16:08:02 -0400 (AST) (envelope-from news) From: Aldor X-Newsgroups: pgsql.admin Subject: Re: autovacuum running even when not set in config? Date: Sun, 16 Dec 2007 21:07:40 +0100 Organization: Hub.Org Networking Services Lines: 17 Message-ID: References: <20071210183551.GA11514@nemesis.aod.cx> <20071210184845.GC27126@alvh.no-ip.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <20071210184845.GC27126@alvh.no-ip.org> To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/136 X-Sequence-Number: 27653 Well, the database is also showing a hint when less then 9 million transactions are available - and this hint is telling us to vacuum the whole database. If, vacuum the whole database, would take days (quite unsure how many days sometimes) is it possible to find out manually which tables originally need a vacuum or is the xid wraparound problem database wide so we MUST vacuum the whole database? The automatic startup of autovacuum in this cases is really good, but we would like to manage vacuum by ourself, especially WHEN it is running, because we have different load times on different database servers depending on time zones and the users using it. > It is normal if the database is in danger of Xid wraparound. (So now > you know have been neglecting to vacuum some tables). >