TimescaleDB allows you to copy existing chunks to a new location within a multi-node environment. This allows each data node to work both as a primary for some chunks and backup for others. If a data node fails, its chunks already exist on other nodes that can take over the responsibility of serving them.


Experimental features could have bugs! They might not be backwards compatible, and could be removed in future releases. Use these features at your own risk, and do not use any experimental features in production.

Required arguments

chunkREGCLASSName of chunk to be copied
source_nodeNAMEData node where the chunk currently resides
destination_nodeNAMEData node where the chunk is to be copied

Sample usage

CALL timescaledb_experimental.copy_chunk(‘_timescaledb_internal._dist_hyper_1_1_chunk’, ‘data_node_2’, ‘data_node_3’);

Found an issue on this page?

Report an issue!

Related Content