X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id A2384D1B531 for ; Sat, 4 Oct 2003 03:49:51 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 04563-06 for ; Sat, 4 Oct 2003 00:49:04 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 34EEDD1B4E2 for ; Sat, 4 Oct 2003 00:49:04 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id h943n3hn003071; Fri, 3 Oct 2003 23:49:03 -0400 (EDT) To: Neil Conway Cc: Christopher Browne , PostgreSQL Performance Subject: Re: reindex/vacuum locking/performance? In-reply-to: <1065224887.387.45.camel@tokyo> References: <16253.56074.737161.470428@jump.bivio.com> <60d6de9fah.fsf@dev6.int.libertyrms.info> <1065224887.387.45.camel@tokyo> Comments: In-reply-to Neil Conway message dated "Fri, 03 Oct 2003 19:48:07 -0400" Date: Fri, 03 Oct 2003 23:49:03 -0400 Message-ID: <3070.1065239343@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/131 X-Sequence-Number: 3879 Neil Conway writes: > On Fri, 2003-10-03 at 17:34, Christopher Browne wrote: >> Not surprising either. While the reindex takes place, updates to that >> table have to be deferred. > Right, but that's no reason not to let SELECTs proceed, for example. What if said SELECTs are using the index in question? I suspect it is true that REINDEX locks more than it needs to, but we should tread carefully about loosening it. regards, tom lane