From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: pgsql-admin@postgresql.org
Subject: Re: Best practice - Vacuum. Replication suggestions and pg vs mysql
Date: Thu, 17 Mar 2005 22:38:22 -0800
Message-ID: <d1dsv0$q0v$1@news.hub.org> (raw)
In-Reply-To: <27132.1111091610@sss.pgh.pa.us>
References: <c76ea21c05031712092663f1e8@mail.gmail.com>
<27132.1111091610@sss.pgh.pa.us>
Tom Lane wrote:
> David B <davidb999@gmail.com> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: rm_pg@cheapcomplexdevices.com
Subject: Re: Best practice - Vacuum. Replication suggestions and pg vs mysql
In-Reply-To: <d1dsv0$q0v$1@news.hub.org>
References: <c76ea21c05031712092663f1e8@mail.gmail.com> <27132.1111091610@sss.pgh.pa.us> <d1dsv0$q0v$1@news.hub.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox