Skip to main content
TimescaleDB allows you to move data and indexes to different tablespaces. This allows you to move data to more cost-effective storage as it ages. The move_chunk function acts like a combination of the CLUSTER command and ALTER TABLE…SET TABLESPACE commands. Unlike these commands, however, the move_chunk function uses lower lock levels so that the and are able to be read for most of the process. This comes at a cost of slightly higher disk usage during the operation. For a more detailed discussion of this capability, see the documentation on managing storage with tablespaces.
You must be logged in as a super user, such as the postgres user, to use the move_chunk() call.

​
Samples

SELECT move_chunk(
  chunk => '_timescaledb_internal._hyper_1_4_chunk',
  destination_tablespace => 'tablespace_2',
  index_destination_tablespace => 'tablespace_3',
  reorder_index => 'conditions_device_id_time_idx',
  verbose => TRUE
);

​
Arguments

NameTypeDefaultRequiredDescription
chunkREGCLASS-✔Name of to be moved
destination_tablespaceNAME-✔Target tablespace for being moved
index_destination_tablespaceNAME-✔Target tablespace for index associated with the you are moving
reorder_indexREGCLASS-✖The name of the index (on either the or ) to order by
verboseBOOLEANFALSE✖Setting to true displays messages about the progress of the move_chunk command.