Re: Side effects of moving an index to a new tablespace - Mailing list pgsql-general

From Sergey Konoplev
Subject Re: Side effects of moving an index to a new tablespace
Date
Msg-id CAL_0b1tCHZ=YCkj2J=feK1vNEHTepFjyyx-eJ7N3rLs9Wn8VGA@mail.gmail.com
Whole thread Raw
In response to Re: Side effects of moving an index to a new tablespace  (Ondrej Ivanič <ondrej.ivanic@gmail.com>)
List pgsql-general
2012/1/10 Ondrej Ivanič <ondrej.ivanic@gmail.com>:
>> One area where the documentation is not very detailed - What are the side
>> effects and/or constraints put in place while an index is being moved? I
>> assume that the index will not be available to the query planner/engine
>> during that time period. Are there other ways in which the table (and other
>> indices) are affected or locked?
>
> yes, you are right there is not too much about "alter index" locking
> in the docs. When I did this last time (PG 8.4) 'alter index' acquired
>  'ACCESS EXCLUSIVE' lock.

To avoid it I usually do CREATE INDEX ... TABLESPACE ... / DROP INDEX
... / ALTER INDEX ... RENAME ...

>
> --
> Ondrej Ivanic
> (ondrej.ivanic@gmail.com)
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general



--
Sergey Konoplev

Blog: http://gray-hemp.blogspot.com
LinkedIn: http://ru.linkedin.com/in/grayhemp
JID/GTalk: gray.ru@gmail.com Skype: gray-hemp

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: How do you change the size of the WAL files?
Next
From: Craig Ringer
Date:
Subject: Re: Time to move table to new tablespace