Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 9E8722E00D4 for ; Mon, 17 Dec 2007 10:55:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 59741-02 for ; Mon, 17 Dec 2007 10:55:26 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 0E3E02E2F24 for ; Mon, 17 Dec 2007 10:55:31 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-76-117.bk5-dsl.surnet.cl [200.126.76.117]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id lBHEtRfr023828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Dec 2007 06:55:30 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id DEF5D47C88; Mon, 17 Dec 2007 11:55:27 -0300 (CLST) Date: Mon, 17 Dec 2007 11:55:27 -0300 From: Alvaro Herrera To: Aldor Cc: pgsql-admin@postgresql.org Subject: Re: autovacuum running even when not set in config? Message-ID: <20071217145527.GI5637@alvh.no-ip.org> References: <20071210183551.GA11514@nemesis.aod.cx> <20071210184845.GC27126@alvh.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Mon, 17 Dec 2007 06:55:30 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/138 X-Sequence-Number: 27655 Aldor wrote: > 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? On 8.2 this is per table. You can check which tables need vacuum with select age(relfreezexid) from pg_class (I'm not sure if the column is relfreezexid or relfrozenxid). > 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. Yeah, this is something we are planning for 8.4. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.