Hello Team,
After upgrading to the latest TimescaleDB version (2.11.2), I’ve noticed that my database logs are filling up with repetitive messages, including:
These logs appear continuously during parallel ingestion and querying, leading to excessive log volume.
Is this expected behaviour in the latest version or is something wrong with policies running, or is there a way to reduce these repetitive logs? Any insights on how to manage or suppress these messages would be greatly appreciated, as we haven’t seen these messages before performing an upgrade.
- deleted 0 row(s)
- inserted 0 row(s)
- recompress_chunk_segmentwise
Environment:
PostgresMajor: 15
Timescale: 2.11.2
LOG: continuous aggregate refresh (individual invalidation) on "hierarchical_values_summary_five_minutes" in window [ 2024-12-16 08:10:00+00, 2024-12-16 08:15:00+00 ]
2024-12-16 08:16:07.370 UTC [3257] LOG: deleted 0 row(s) from materialization table "_timescaledb_internal._materialized_hypertable_4"
2024-12-16 08:16:07.372 UTC [3257] LOG: inserted 0 row(s) into materialization table "_timescaledb_internal._materialized_hypertable_4"
2024-12-16 08:16:09.736 UTC [3259] LOG: continuous aggregate refresh (individual invalidation) on "hierarchical_values_summary_one_minute" in window [ 2024-12-16 08:14:00+00, 2024-12-16 08:15:00+00 ]
2024-12-16 08:16:09.737 UTC [3259] LOG: deleted 0 row(s) from materialization table "_timescaledb_internal._materialized_hypertable_3"
2024-12-16 08:16:09.739 UTC [3259] LOG: inserted 0 row(s) into materialization table "_timescaledb_internal._materialized_hypertable_3"
2024-12-16 08:17:09.749 UTC [3278] LOG: continuous aggregate refresh (individual invalidation) on "hierarchical_values_summary_one_minute" in window [ 2024-12-16 08:15:00+00, 2024-12-16 08:16:00+00 ]
2024-12-16 08:17:09.750 UTC [3278] LOG: deleted 0 row(s) from materialization table "_timescaledb_internal._materialized_hypertable_3"
2024-12-16 08:17:09.751 UTC [3278] LOG: inserted 0 row(s) into materialization table "_timescaledb_internal._materialized_hypertable_3"
During parallel ingestion and querying observed below log continuously.
2024-12-16 07:40:09.173 UTC [2562] LOG: finished compressing 261 rows from "_hyper_8_80_chunk"
2024-12-16 07:40:09.173 UTC [2562] CONTEXT: SQL statement "SELECT _timescaledb_functions.recompress_chunk_segmentwise(chunk_rec.oid)"
PL/pgSQL function _timescaledb_functions.policy_compression_execute(integer,integer,anyelement,integer,boolean,boolean,boolean) line 88 at PERFORM
SQL statement "CALL _timescaledb_functions.policy_compression_execute(
job_id, htid, lag_value::INTERVAL,
maxchunks, verbose_log, recompress_enabled, use_creation_time
)"
PL/pgSQL function _timescaledb_functions.policy_compression(integer,jsonb) line 60 at CALL
2024-12-16 07:40:09.174 UTC [2562] LOG: finished compressing 261 rows from "_hyper_8_80_chunk"
2024-12-16 07:40:09.174 UTC [2562] CONTEXT: SQL statement "SELECT _timescaledb_functions.recompress_chunk_segmentwise(chunk_rec.oid)"
PL/pgSQL function _timescaledb_functions.policy_compression_execute(integer,integer,anyelement,integer,boolean,boolean,boolean) line 88 at PERFORM
SQL statement "CALL _timescaledb_functions.policy_compression_execute(
job_id, htid, lag_value::INTERVAL,
maxchunks, verbose_log, recompress_enabled, use_creation_time
)"
PL/pgSQL function _timescaledb_functions.policy_compression(integer,jsonb) line 60 at CALL
Thank you.