TimeScale Notes: Difference between revisions
Ian.readman (talk | contribs) No edit summary |
Ian.readman (talk | contribs) No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 51: | Line 51: | ||
pg_size_pretty(after_compression_total_bytes) as after | pg_size_pretty(after_compression_total_bytes) as after | ||
FROM hypertable_compression_stats('crypto_ticks'); | FROM hypertable_compression_stats('crypto_ticks'); | ||
SELECT pg_size_pretty(hypertable_size('CRYPTO_TICKS')); | |||
</pre> | </pre> | ||
=== Compression Policy === | === Compression Policy === | ||
Create a scheduled job that will compress all data with a 'time' column that is older than 8 days. </br> | |||
<pre>SELECT add_compression_policy('crypto_ticks', INTERVAL '8 days'); </pre> | <pre>SELECT add_compression_policy('crypto_ticks', INTERVAL '8 days'); </pre> | ||
Latest revision as of 08:55, 8 April 2025
Installation[edit]
https://docs.timescale.com/self-hosted/latest/install/installation-linux
Create Hypertable[edit]
CREATE TABLE conditions ( time TIMESTAMPTZ NOT NULL, location TEXT NOT NULL, temperature DOUBLE PRECISION NULL );
SELECT create_hypertable('conditions', by_range('time')); SELECT create_hypertable('conditions', by_range('time', INTERVAL '1 day')); SELECT set_chunk_time_interval('conditions', INTERVAL '2 days');
The default time interval for a chunk is 7 days.
The dimension can either be by_range or by_hash.
Indexes[edit]
You can create indexes on Hyper Tables as per normal.
However when creating a unique index you must include the partioning columns
In the example above that would include the time column.
Compression[edit]
Check Distinct Values[edit]
-- n_distinct (-1 = Unique, 1 = All The Same) SELECT tablename, attname, most_common_vals, most_common_freqs, n_distinct FROM pg_stats -- WHERE tablename = '<TableName>'; WHERE schemaname = '<SchemaName>';
Compress Table[edit]
ALTER TABLE crypto_ticks SET (timescaledb.compress, timescaledb.compress_segmentby='symbol', timescaledb.compress_orderby='time DESC');
SELECT compress_chunk(c) from show_chunks('crypto_ticks') c;
Check Compression[edit]
SELECT pg_size_pretty(before_compression_total_bytes) as before, pg_size_pretty(after_compression_total_bytes) as after FROM hypertable_compression_stats('crypto_ticks'); SELECT pg_size_pretty(hypertable_size('CRYPTO_TICKS'));
Compression Policy[edit]
Create a scheduled job that will compress all data with a 'time' column that is older than 8 days.
SELECT add_compression_policy('crypto_ticks', INTERVAL '8 days');
Links[edit]
https://docs.timescale.com/tutorials/latest/financial-tick-data/financial-tick-compress
Since version 2.18, HyperCore has been used for compression.
This uses a hybrid of row and columnar storage.
https://docs.timescale.com/use-timescale/latest/compression (Old)
https://docs.timescale.com/use-timescale/latest/hypercore] (New)