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 63F11D1B51A for ; Fri, 3 Oct 2003 23:48:54 +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 73778-04 for ; Fri, 3 Oct 2003 20:48:10 -0300 (ADT) Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by svr1.postgresql.org (Postfix) with ESMTP id 86CEFD1B533 for ; Fri, 3 Oct 2003 20:48:07 -0300 (ADT) Received: from 6-allhosts (d226-85-166.home.cgocable.net [24.226.85.166]) by bob.samurai.com (Postfix) with ESMTP id 225431DA9; Fri, 3 Oct 2003 19:48:10 -0400 (EDT) Subject: Re: reindex/vacuum locking/performance? From: Neil Conway To: Christopher Browne Cc: PostgreSQL Performance In-Reply-To: <60d6de9fah.fsf@dev6.int.libertyrms.info> References: <16253.56074.737161.470428@jump.bivio.com> <60d6de9fah.fsf@dev6.int.libertyrms.info> Content-Type: text/plain Message-Id: <1065224887.387.45.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Fri, 03 Oct 2003 19:48:07 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/125 X-Sequence-Number: 3873 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. (Whether that would actually be *useful* is another question...) -Neil