Move chunks() to different table space will reduce disk storage

TimescaleDB and PostgreSQL
,
1

I’m using my local machine for timescaledb now I want to reduce disk space so I want to move old chunks to new table space to reduce storage (Timescale Documentation | Manage storage using tablespaces), so I moved old chunks to new table space using move chunk() command after this I ran VACUUM FULL on my hypertable .
After doing this I checked my db space is showing same size it is not got reduced using SELECT * FROM hypertable_detailed_size(‘my_hypertable’); command. So I want to ask few quetions

  1. move chunks()(older chunks) to different table space will reduce the size of the disk space or hypertable?
  2. should I need to run VACUUM FULL command after running move chunks() command, is it required?
  3. I want to move older chunks to s3 bucket using mount s3 to aws ec2 instance is it reduce the disk space of my ec2 instance.
2

Moving chunks to a different tablespace does not inherently reduce the data size or the hypertable. It simply relocates the data to a different storage location. The total size of the data remains the same; it’s just stored in a different place.

The purpose of moving chunks to a different tablespace is typically to manage storage more efficiently. For example, older, less frequently accessed data can be moved to slower, cheaper storage while more recent, frequently accessed data can be kept on faster storage.

Running VACUUM FULL after move_chunks() is not strictly necessary, but it can help reclaim space if there are a lot of dead tuples (rows that have been deleted or updated) in the chunks you moved. However, VACUUM FULL can be pretty expensive regarding time and resources, as it rewrites the entire table to remove dead tuples and compact the data.

If you aim to reduce disk space, VACUUM FULL can help, but it’s not directly related to the move_chunks() operation. You might want to consider running VACUUM (without FULL) first, which is less aggressive and can still help with space reclamation.

You may also consider aggregating your data and removing raw data, establishing a retention policy.

Check tiered storage, but it’s only available on Timescale Cloud.