Tiered data is stored on our object storage tier. Tiered data is immutable, and cannot
be changed. To update data in a tiered chunk, you need to move it back to local storage (Timescale's standard high-performance storage tier).
This is called untiering the data. You can untier data in a chunk using the untier_chunk
stored procedure.
Untiering chunks is a synchronous process that occurs when the untier_chunk
procedure is called. When you untier a chunk, the data is moved from the object storage tier
to local storage. Chunks are renamed when the data is untiered.
At the
psql
prompt, check which chunks are currently tiered:SELECT * FROM timescaledb_osm.tiered_chunks ;The output looks something like this:
hypertable_schema | hypertable_name | chunk_name | range_start | range_end-------------------+-----------------+------------------+------------------------+------------------------public | sample | _hyper_1_1_chunk | 2023-02-16 00:00:00+00 | 2023-02-23 00:00:00+00(1 row)Run
untier_chunk
:CALL untier_chunk('_hyper_1_1_chunk');You can see the details of the chunk with the
timescaledb_information.chunks
function. The chunk might have changed name when it was untiered:SELECT * FROM timescaledb_information.chunks;The output looks something like this:
-[ RECORD 1 ]----------+-------------------------hypertable_schema | publichypertable_name | samplechunk_schema | _timescaledb_internalchunk_name | _hyper_1_4_chunkprimary_dimension | tsprimary_dimension_type | timestamp with time zonerange_start | 2023-02-16 00:00:00+00range_end | 2020-03-23 00:00:00+00range_start_integer |range_end_integer |is_compressed | fchunk_tablespace |data_nodes |
Keywords
Found an issue on this page?
Report an issue!