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

From Jason Buberel
Subject Side effects of moving an index to a new tablespace
Date
Msg-id CAAPEApHVk1VzrMkUqqcuQBoh0T=iJnYai=u5o2CwuVdHKxgN2A@mail.gmail.com
Whole thread Raw
Responses Re: Side effects of moving an index to a new tablespace  (Ondrej Ivanič <ondrej.ivanic@gmail.com>)
List pgsql-general
As per Ondrej's suggestion, our current thinking/planning at this point is to move indices instead of tables. 

We have lots of them, they are much smaller than the tables, and that will allow us to do the migrations more incrementally.

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?

Cheers,
jason 


pgsql-general by date:

Previous
From: Andy Chambers
Date:
Subject: Re: Update takes longer than expected
Next
From: rama
Date:
Subject: Re: How do you change the size of the WAL files?