Side effects of moving an index to a new tablespace

From: Jason Buberel <jason(at)altosresearch(dot)com>
To: PostgreSQL <pgsql-general(at)postgresql(dot)org>
Cc: "Tom Sparks (Applied Operations)" <tsparks(at)appliedops(dot)net>
Subject: Side effects of moving an index to a new tablespace
Date: 2012-01-09 22:16:18
Message-ID: CAAPEApHVk1VzrMkUqqcuQBoh0T=iJnYai=u5o2CwuVdHKxgN2A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ondrej Ivanič 2012-01-09 23:49:09 Re: Side effects of moving an index to a new tablespace
Previous Message Andy Chambers 2012-01-09 22:13:06 Re: Update takes longer than expected