Search Postgresql Archives

Side effects of moving an index to a new tablespace

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux