X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 090D69DCA09 for ; Wed, 18 Jan 2006 13:04:11 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 84455-01 for ; Wed, 18 Jan 2006 13:04:07 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 70E009DC833 for ; Wed, 18 Jan 2006 13:04:05 -0400 (AST) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 7D0A33094B; Wed, 18 Jan 2006 18:04:04 +0100 (MET) From: Chris Browne X-Newsgroups: pgsql.performance Subject: Re: Autovacuum / full vacuum Date: Wed, 18 Jan 2006 11:54:21 -0500 Organization: cbbrowne Computing Inc Lines: 30 Message-ID: <60d5ipcw8y.fsf@dba2.int.libertyrms.com> References: <20060117145649.GE21092@phlogiston.dyndns.org> <608xteerfh.fsf@dba2.int.libertyrms.com> <20060117173046.GA4296@surnet.cl> <604q42elzl.fsf@dba2.int.libertyrms.com> <20592.1137526372@sss.pgh.pa.us> <034701c61c46$f427df20$f20214ac@bite.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, linux) Cancel-Lock: sha1:FRDAIcROqayiJU6iWG92L5oMhVk= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.247 required=5 tests=[AWL=0.247] X-Spam-Score: 0.247 X-Spam-Level: X-Archive-Number: 200601/301 X-Sequence-Number: 16779 mind@bi.lt ("Mindaugas") writes: >> >> Even a database-wide vacuum does not take locks on more than one >> >> table. The table locks are acquired and released one by one, as >> >> the operation proceeds. >> >> > Has that changed recently? I have always seen "vacuumdb" or SQL >> > "VACUUM" (without table specifications) running as one long >> > transaction which doesn't release the locks that it is granted >> > until the end of the transaction. >> >> You sure? It's not supposed to, and watching a database-wide >> vacuum with "select * from pg_locks" doesn't look to me like it >> ever has locks on more than one table (plus the table's indexes and >> toast table). > > Are there some plans to remove vacuum altogether? I don't see that on the TODO list... http://www.postgresql.org/docs/faqs.TODO.html To the contrary, there is a whole section on what functionality to *ADD* to VACUUM. -- let name="cbbrowne" and tld="acm.org" in String.concat "@" [name;tld];; http://www.ntlug.org/~cbbrowne/finances.html "There are two types of hackers working on Linux: those who can spell, and those who can't. There is a constant, pitched battle between the two camps." --Russ Nelson (Linux Kernel Summary, Ver. 1.1.75 -> 1.1.76)