Thread: Re: ALTER INDEX set fillfactor

> ------- Original Message -------
> From: Simon Riggs <simon@2ndquadrant.com>
> To: Dave Page <dpage@postgresql.org>
> Sent: 06/10/07, 08:33:30
> Subject: Re: [pgadmin-hackers] ALTER INDEX set  fillfactor
>
> On Fri, 2007-10-05 at 21:24 +0100, Dave Page wrote:
> > Simon Riggs wrote:
>
> > > It would be even better if there was an option to do that CONCURRENTLY,
> > > i.e. add the new index and then drop the old one afterwards. (It's
> > > unfortunate that there isn't a REINDEX concurrently, but there isn't
> > > yet).
> >
> > Funny - I suggested that to Greg just the other day...
>
> Sorry, I meant in the absence of REINDEX concurrently, we can issue:
>
> CREATE INDEX CONCURRENTLY newindex
> DROP INDEX oldindex
>
> on each index on the table in turn, which does the same thing.

CIC can't be run in a transaction block, so how do we queue up the drop & rename to run after it completes? Given the
changesto VACUUM & CREATE DATABASE/TABLESPACE in 8.3 I would imagine it won't run in a multi-statement query either
now.

/D

On Sat, 2007-10-06 at 17:45 +0100, Dave Page wrote:

> CIC can't be run in a transaction block, so how do we queue up the
> drop & rename to run after it completes?

> Given the changes to VACUUM & CREATE DATABASE/TABLESPACE in 8.3 I
> would imagine it won't run in a multi-statement query either now.

Sounds like we need the ability to run multiple commands one after the
other before we do that. Shame we lost the multi-stmt query, but it was
correct to do that.

--
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com