X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 591FC5341B for ; Fri, 25 Mar 2005 23:17:26 +0000 (GMT) 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 97230-08 for ; Fri, 25 Mar 2005 23:17:16 +0000 (GMT) Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id 34C8B52A69 for ; Fri, 25 Mar 2005 23:17:15 +0000 (GMT) Received: from 192.168.1.52 (fc1smp [66.93.38.87]) by hosting.commandprompt.com (8.12.8/8.12.8) with ESMTP id j2PNE6kh022250; Fri, 25 Mar 2005 15:14:06 -0800 Subject: Re: pg_autovacuum not having enough suction ? From: "Joshua D. Drake" Reply-To: jd@commandprompt.com To: Bruce Momjian Cc: Tom Lane , "Matthew T. O'Connor" , Otto Blomqvist , "pgsql-performance@postgresql.org" In-Reply-To: <200503252313.j2PNDFA24795@candle.pha.pa.us> References: <200503252313.j2PNDFA24795@candle.pha.pa.us> Content-Type: text/plain Organization: Joshua D. Drake Date: Fri, 25 Mar 2005 15:17:06 -0800 Message-Id: <1111792626.5783.11.camel@jd2.commandprompt.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.036 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/571 X-Sequence-Number: 11276 > > I'm not sure if autovacuum could be taught to do that --- it could > > perhaps launch a vacuum as soon as it notices a large fraction of the > > table got deleted, but do we really want to authorize it to launch > > VACUUM FULL? It'd be better to issue the vacuum synchronously > > as part of the batch updating script, I feel. > > I added this to the TODO section for autovacuum: > > o Do VACUUM FULL if table is nearly empty? We should never automatically launch a vacuum full. That seems like a really bad idea. Sincerely, Joshua D. Drake > > I don't think autovacuum is every going to be smart enough to recycle > during the delete, especially since the rows can't be reused until the > transaction completes. > > One problem with VACUUM FULL would be autovacuum waiting for an > exclusive lock on the table. Anyway, it is documented now as a possible > issue. > -- Command Prompt, Inc., Your PostgreSQL solutions company. 503-667-4564 Custom programming, 24x7 support, managed services, and hosting Open Source Authors: plPHP, pgManage, Co-Authors: plPerlNG Reliable replication, Mammoth Replicator - http://www.commandprompt.com/