From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Mayer <rm_pg@cheapcomplexdevices.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Best practice - Vacuum. Replication suggestions and pg vs mysql
Date: Fri, 18 Mar 2005 02:04:14 -0500
Message-ID: <3780.1111129454@sss.pgh.pa.us> (raw)
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>
Ron Mayer <rm_pg@cheapcomplexdevices.com> writes:
> Tom Lane wrote:
>> 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.
Good point --- gist (and rtree) indexes still don't have any support for
concurrent updates, so they have to be locked while VACUUM scans them.
> 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.
Perhaps. VACUUM going at full tilt would cause a system-wide
performance impact, though, while the lock only affects processes
trying to use or update that index. So you could argue it either
way.
The best solution would be to fix GIST ;-)
regards, tom lane
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: tgl@sss.pgh.pa.us, rm_pg@cheapcomplexdevices.com
Subject: Re: Best practice - Vacuum. Replication suggestions and pg vs mysql
In-Reply-To: <3780.1111129454@sss.pgh.pa.us>
References: <c76ea21c05031712092663f1e8@mail.gmail.com> <27132.1111091610@sss.pgh.pa.us> <d1dsv0$q0v$1@news.hub.org> <3780.1111129454@sss.pgh.pa.us>
* 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