pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Neil Conway <neilc@samurai.com>
To: Christopher Browne <cbbrowne@libertyrms.info>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: reindex/vacuum locking/performance?
Date: Fri, 03 Oct 2003 19:48:07 -0400
Message-ID: <1065224887.387.45.camel@tokyo> (raw)
In-Reply-To: <60d6de9fah.fsf@dev6.int.libertyrms.info>
References: <16253.56074.737161.470428@jump.bivio.com>
	<60d6de9fah.fsf@dev6.int.libertyrms.info>

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





view thread (37+ messages)  latest in thread

Message-ID: <1065224887.387.45.camel@tokyo>
Permalink:  ../1065224887.387.45.camel@tokyo/
Also on:    postgresql.org/message-id/1065224887.387.45.camel@tokyo

 · 

reply

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, cbbrowne@libertyrms.info
  Subject: Re: reindex/vacuum locking/performance?
  In-Reply-To: <1065224887.387.45.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