yinan8128
yinan8128
Hi Thank you for the information If we change the compress_segmentby column, if have to change the primary key please? As this ticket https://github.com/timescale/timescaledb/issues/5892, our existing compress_segmentby column id is...
Hello Thank you for your information As change compress_segmentby column need to decompress chunks firstly 1. If truncate compressed chunks and their original chunk before decompression can reduce the deployment...
Hello Thank you for the information So truncate compressed chunks and their original chunk before decompression can reduce the deployment time: 1. Is there method to drop all compressed chunks...
After our local test env use date column, the table size decreased, but after go to production, after compression still caused storage increased, will check and update here
Found the root caused is that date column values are almost unique in production
How about the relationship of compression rate, query efficiency and data? For example 10000 records: 1. 1000 unique values, each value 10 records 2. 100 unique values, each value 100...
Hi Thank you for your reply vacuum script ``` select 'vacuum verbose'||' '||chunk_schema||'.'||chunk_name||';' from timescaledb_information.chunks where hypertable_name='tag' order by hypertable_name,chunk_name; ?column? ----------------------------------------------------------- vacuum verbose _timescaledb_internal._hyper_19_10_chunk; vacuum verbose _timescaledb_internal._hyper_19_246_chunk; vacuum verbose...
Hi Thank you for your reply 1. We checked timescaledb_information.job_errors, there are no error log of 2023-06-30, but still some compression problem happened in 2023-06-30, is it possible that timescaledb_information.job_errors...
Hi Thank you for the update We already disabled the compression in the production env, let's check another production env which have problem and feedback to you
Hi In our one env, there is database size increase problem after compression, retention reduce some storage size, but storage size usage trend is increasing, sooner or later will hit...