Re: Vacuum (table performance)

> > An alternative suggested right there is to drop and recreate an index,
> > where -it says- CREATE INDEX would get a write lock on the table. Does
>this
> > mean that during the create index operation the whole table is
>unavailable
> > for write by other processes?
>
>An alternative approach would be to create a second index indentical to
>the one in place and drop the first one.
>

OK, but what's the difference in creating a second index and dropping the
original one first and recreate it? If I understood correctly the doc, I
think the table will be unavailable for write in either case, is this right?

cl.

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus