pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ashley Moran <ashley.moran@codeweavers.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: REINDEX during a transaction
Date: Wed, 1 Mar 2006 13:21:33 -0600
Message-ID: <20060301192133.GL82012@pervasive.com> (raw)
In-Reply-To: <10725.1141226621@sss.pgh.pa.us>
References: <200602211250.44749.ashley.moran@codeweavers.net>
	<10725.1141226621@sss.pgh.pa.us>

On Wed, Mar 01, 2006 at 10:23:41AM -0500, Tom Lane wrote:
> Ashley Moran <ashley.moran@codeweavers.net> writes:
> > BEGIN WORK;
> > DELETE FROM X; COPY X ...; REINDEX TABLE X;
> > DELETE FROM Y; COPY Y ...; REINDEX TABLE Y;
> > DELETE FROM Z; COPY Z ...; REINDEX TABLE Z;
> > COMMIT;
> 
> Why don't you use TRUNCATE?  Why do you think you need REINDEX at all?
> 
> If you do need it, you'd be best off to drop the indexes, truncate,
> copy, re-create the indexes.  See
> http://www.postgresql.org/docs/8.1/static/populate.html#POPULATE-RM-INDEXES

And to answer some of your original question, I don't believe there's
any advantage to wrapping the REINDEXes into the transaction. If can't
use Tom's suggestion of dropping the indexes before the COPY, you might
want to instead create new indexes with the same definition of existing
ones, and then drop the old ones; readers of the table will react
differently to the two.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (3+ messages)

Message-ID: <20060301192133.GL82012@pervasive.com>
Permalink:  ../20060301192133.GL82012@pervasive.com/
Also on:    postgresql.org/message-id/20060301192133.GL82012@pervasive.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, tgl@sss.pgh.pa.us, ashley.moran@codeweavers.net
  Subject: Re: REINDEX during a transaction
  In-Reply-To: <20060301192133.GL82012@pervasive.com>
  References: <200602211250.44749.ashley.moran@codeweavers.net> <10725.1141226621@sss.pgh.pa.us> <20060301192133.GL82012@pervasive.com>

* 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