Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 599F92E0101 for ; Fri, 22 Feb 2008 11:44:51 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 00661-05 for ; Fri, 22 Feb 2008 11:44:48 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 3318A2E00FD for ; Fri, 22 Feb 2008 11:44:48 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-103-57.bk7-dsl.surnet.cl [200.126.103.57]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m1MFirnp027726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 22 Feb 2008 07:44:58 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id CC38F47BF6; Fri, 22 Feb 2008 12:44:30 -0300 (CLST) Date: Fri, 22 Feb 2008 12:44:30 -0300 From: Alvaro Herrera To: Mikko Partio Cc: pgsql-admin@postgresql.org Subject: Re: Stray autovacuum daemon Message-ID: <20080222154430.GD9392@alvh.no-ip.org> References: <2ca799770802220305v38b800dbt909c84e3b3be57cc@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2ca799770802220305v38b800dbt909c84e3b3be57cc@mail.gmail.com> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Fri, 22 Feb 2008 07:44:58 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/277 X-Sequence-Number: 28351 Mikko Partio escribió: > Now, the problem is that I cannot turn autovacuum off! I have tried to set > autovacuum = off at postgresql.conf with no avail. I have also tried to > disable the vacuum by inserting rows to pg_autovacuum but still the vacuum > processes just pop up. What's even more weird is that autovacuum is > vacuuming the same tables over and over. No sign of xid wraparound issues > show in the logs. How can I stop autovacuum without restarting the database > instance? If your database is in danger of Xid wraparound, autovacuum will run on it no matter what you do. Check pg_class.relfrozenxid and pg_database.datfrozenxid, and the current Xid counter (from pg_controldata I think). Also take a look at the description of the autovacuum_min_freeze_age param (or was it max_freeze_age? I forget). -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support