From: Neil Conway <neilc@samurai.com>
To: Allen Landsidel <all@biosys.net>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: My own performance/tuning q&a
Date: Mon, 27 Oct 2003 11:07:39 -0500
Message-ID: <1067270858.460.39.camel@tokyo> (raw)
In-Reply-To: <6.0.0.22.0.20031024194443.024306b8@pop.hotpop.com>
References: <16281.22423.26659.54130@yertle.int.kciLink.com>
<200310242050.h9OKoYX22829@candle.pha.pa.us>
<6.0.0.22.0.20031024194443.024306b8@pop.hotpop.com>
On Fri, 2003-10-24 at 20:11, Allen Landsidel wrote:
> However, I do the same thing with the reindex, so I'll definitely be taking
> it out there, as that one does lock.. although I would think the worst this
> would do would be a making the index unavailable and forcing a seq scan..
> is that not the case?
No, it exclusively locks the table. It has been mentioned before that we
should probably be able to fall back to a seqscan while the REINDEX is
going on, but that's not currently done.
-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, all@biosys.net
Subject: Re: My own performance/tuning q&a
In-Reply-To: <1067270858.460.39.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