X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AD2D956559 for ; Fri, 18 Mar 2005 06:41:30 +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 25842-03 for ; Fri, 18 Mar 2005 06:41:22 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 1F11A56556 for ; Fri, 18 Mar 2005 06:41:22 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j2I6fLdD027357 for ; Fri, 18 Mar 2005 06:41:21 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j2I6bKNU026656 for pgsql-admin@postgresql.org; Fri, 18 Mar 2005 06:37:20 GMT (envelope-from news) From: Ron Mayer X-Newsgroups: pgsql.admin Subject: Re: Best practice - Vacuum. Replication suggestions and pg vs mysql Date: Thu, 17 Mar 2005 22:38:22 -0800 Organization: Hub.Org Networking Services Lines: 18 Message-ID: References: <27132.1111091610@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en In-Reply-To: <27132.1111091610@sss.pgh.pa.us> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200503/284 X-Sequence-Number: 16782 Tom Lane wrote: > David B writes: >>15minute lock is a long time. > There's no lock, unless you are using VACUUM FULL which you shouldn't. Or, I believe, if he has any GIST indexes (such as tsearch or postgis ones). At least it seems normal vacuum locks GIST indexes for quite some time here. I ended up stopping using vacuum_cost_delay to minimize the time those GIST indexes seemed locked. Ron PS: If I'm right, I wonder if VACUUM or at least autovacuum should automatically force vacuum_cost_delay to zero while holding locks (i.e. while doing GIST indexes) to reduce the time those locks are held.