From 9ef84d9bf2b5bc302c8045598335e2098764ff66 Mon Sep 17 00:00:00 2001 From: XbaoWu Date: Fri, 17 Jan 2025 15:49:29 +0800 Subject: [PATCH] Fix configuration name --- api/enable_chunk_skipping.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/api/enable_chunk_skipping.md b/api/enable_chunk_skipping.md index 587aaeb7d8..c5de71992d 100644 --- a/api/enable_chunk_skipping.md +++ b/api/enable_chunk_skipping.md @@ -38,7 +38,7 @@ A [decompress_chunk][decompress_chunk] invocation on a compressed chunk resets i from the `chunk_column_stats` catalog table since now it's available for DML and the min/max range values can change on any further data manipulation in the chunk. -By default, this feature is disabled. To enable chunk skipping, set `timescale.enable_chunk_skipping = on` in +By default, this feature is disabled. To enable chunk skipping, set `timescaledb.enable_chunk_skipping = on` in `postgresql.conf`. When you upgrade from a database instance that uses compression but does not support chunk skipping, you need to recompress the previously compressed chunks for chunk skipping to work.