From: Neil Conway <neilc@samurai.com>
To: Rob Nagler <nagler@bivio.biz>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: reindex/vacuum locking/performance?
Date: Fri, 03 Oct 2003 18:11:45 -0400
Message-ID: <1065219105.3068.43.camel@tokyo> (raw)
In-Reply-To: <16253.61013.56254.526139@jump.bivio.com>
References: <16253.56074.737161.470428@jump.bivio.com>
<954.1065214676@sss.pgh.pa.us>
<16253.61013.56254.526139@jump.bivio.com>
On Fri, 2003-10-03 at 17:47, Rob Nagler wrote:
> They don't deadlock normally,
> only with reindex and vacuum did I see this behavior.
If you can provide a reproducible example of a deadlock induced by
REINDEX + VACUUM, that would be interesting.
(FWIW, I remember noticing a potential deadlock in the REINDEX code and
posting to -hackers about it, but I've never seen it occur in a
real-world situation...)
> One other question: The reindex seems to lock the table for the entire
> process as opposed to freeing the lock between index rebuilds.
Yeah, I wouldn't be surprised if there is some room for optimizing the
locks that are acquired by REINDEX.
-Neil
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: neilc@samurai.com, nagler@bivio.biz
Subject: Re: reindex/vacuum locking/performance?
In-Reply-To: <1065219105.3068.43.camel@tokyo>
* 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