X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C35FCD1B564 for ; Mon, 27 Oct 2003 16:08:17 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 75074-06 for ; Mon, 27 Oct 2003 12:07:46 -0400 (AST) Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by svr1.postgresql.org (Postfix) with ESMTP id 47BCAD1B55F for ; Mon, 27 Oct 2003 12:07:46 -0400 (AST) Received: from 6-allhosts (d226-89-59.home.cgocable.net [24.226.89.59]) by bob.samurai.com (Postfix) with ESMTP id 662461F92; Mon, 27 Oct 2003 11:07:45 -0500 (EST) Subject: Re: My own performance/tuning q&a From: Neil Conway To: Allen Landsidel Cc: PostgreSQL Performance 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> Content-Type: text/plain Message-Id: <1067270858.460.39.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 27 Oct 2003 11:07:39 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/676 X-Sequence-Number: 4424 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