From 28d69dcc4f7df17826b28db605d94f06fbaae5cb Mon Sep 17 00:00:00 2001
From: Iain <iain@timescale.com>
Date: Wed, 4 Jun 2025 12:09:45 +0200
Subject: [PATCH 1/3] chore: add the chunk_time_interval parameter.

---
 api/continuous-aggregates/alter_materialized_view.md  |  2 +-
 api/continuous-aggregates/create_materialized_view.md | 11 ++++++-----
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/api/continuous-aggregates/alter_materialized_view.md b/api/continuous-aggregates/alter_materialized_view.md
index e59cf68fb8..4f7136c7f4 100644
--- a/api/continuous-aggregates/alter_materialized_view.md
+++ b/api/continuous-aggregates/alter_materialized_view.md
@@ -45,7 +45,7 @@ ALTER MATERIALIZED VIEW <view_name> SET ( timescaledb.<option> =  <value> [, ...
 | `timescaledb.compress_segmentby`           | TEXT                                    | Column list on which to key the compressed segments. An identifier representing the source of the data such as `device_id` or `tags_id` is usually a good candidate. The default is no `segment by` columns.                                                                                                                                                                                                                                       |
 | `timescaledb.compress_chunk_time_interval` | TEXT                                    | EXPERIMENTAL: set compressed chunk time interval used to roll compressed chunks into. This parameter compresses every chunk, and then merges it into a previous adjacent chunk if possible, to reduce the total number of chunks in the hypertable. It should be set to a multiple of the current chunk interval. This option can be changed independently of other compression settings and does not require the `timescaledb.compress` argument. |
 | `timescaledb.enable_cagg_window_functions` | BOOLEAN                                 | EXPERIMENTAL: enable window functions on continuous aggregates. Support is experimental, as there is a risk of data inconsistency if the user is not careful. For example, in backfill scenarios, buckets could be missed. |
-
+| `timescaledb.chunk_time_interval`          |INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.  |
 
 ## Sample usage
 
diff --git a/api/continuous-aggregates/create_materialized_view.md b/api/continuous-aggregates/create_materialized_view.md
index e2ef6b469f..dd85499a98 100644
--- a/api/continuous-aggregates/create_materialized_view.md
+++ b/api/continuous-aggregates/create_materialized_view.md
@@ -75,11 +75,12 @@ Required `WITH` clause options:
 
 Optional `WITH` clause options:
 
-|Name|Type|Description|Default value|
-|-|-|-|-|
-|`timescaledb.materialized_only`|BOOLEAN|Return only materialized data when querying the continuous aggregate view|`TRUE`|
-|`timescaledb.create_group_indexes`|BOOLEAN|Create indexes on the continuous aggregate for columns in its `GROUP BY` clause. Indexes are in the form `(<GROUP_BY_COLUMN>, time_bucket)`|`TRUE`|
-|`timescaledb.finalized`|BOOLEAN|In TimescaleDB 2.7 and above, use the new version of continuous aggregates, which stores finalized results for aggregate functions. Supports all aggregate functions, including ones that use `FILTER`, `ORDER BY`, and `DISTINCT` clauses.|`TRUE`|
+|Name|Type| Description                                                                                                                                                                                                                                |Default value|
+|-|-|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-|
+|`timescaledb.chunk_time_interval`|INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.                                                                                                     |
+|`timescaledb.create_group_indexes`|BOOLEAN| Create indexes on the continuous aggregate for columns in its `GROUP BY` clause. Indexes are in the form `(<GROUP_BY_COLUMN>, time_bucket)`                                                                                                |`TRUE`|
+|`timescaledb.finalized`|BOOLEAN| In TimescaleDB 2.7 and above, use the new version of continuous aggregates, which stores finalized results for aggregate functions. Supports all aggregate functions, including ones that use `FILTER`, `ORDER BY`, and `DISTINCT` clauses. |`TRUE`|
+|`timescaledb.materialized_only`|BOOLEAN| Return only materialized data when querying the continuous aggregate view                                                                                                                                                                  |`TRUE`|
 
 For more information, see the [real-time aggregates][real-time-aggregates] section.
 

From b53045b09fe53a64fdb7246deaf9ea420d9d4ff3 Mon Sep 17 00:00:00 2001
From: Keyur Panchal <keyur@timescale.com>
Date: Thu, 3 Jul 2025 08:57:09 -0600
Subject: [PATCH 2/3] Rename parameter to chunk_interval

---
 api/continuous-aggregates/alter_materialized_view.md  | 2 +-
 api/continuous-aggregates/create_materialized_view.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/api/continuous-aggregates/alter_materialized_view.md b/api/continuous-aggregates/alter_materialized_view.md
index 82f1381706..e16f364ec5 100644
--- a/api/continuous-aggregates/alter_materialized_view.md
+++ b/api/continuous-aggregates/alter_materialized_view.md
@@ -45,7 +45,7 @@ ALTER MATERIALIZED VIEW <view_name> SET ( timescaledb.<option> =  <value> [, ...
 | `timescaledb.compress_segmentby`           | TEXT                                    | Column list on which to key the compressed segments. An identifier representing the source of the data such as `device_id` or `tags_id` is usually a good candidate. The default is no `segment by` columns.                                                                                                                                                                                                                                       |
 | `timescaledb.compress_chunk_time_interval` | TEXT                                    | EXPERIMENTAL: set compressed chunk time interval used to roll compressed chunks into. This parameter compresses every chunk, and then merges it into a previous adjacent chunk if possible, to reduce the total number of chunks in the hypertable. It should be set to a multiple of the current chunk interval. This option can be changed independently of other compression settings and does not require the `timescaledb.compress` argument. |
 | `timescaledb.enable_cagg_window_functions` | BOOLEAN                                 | EXPERIMENTAL: enable window functions on continuous aggregates. Support is experimental, as there is a risk of data inconsistency if the user is not careful. For example, in backfill scenarios, buckets could be missed. |
-| `timescaledb.chunk_time_interval`          |INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.  |
+| `timescaledb.chunk_interval`          |INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.  |
 
 ## Sample usage
 
diff --git a/api/continuous-aggregates/create_materialized_view.md b/api/continuous-aggregates/create_materialized_view.md
index 9bf2a88c51..09855ecaab 100644
--- a/api/continuous-aggregates/create_materialized_view.md
+++ b/api/continuous-aggregates/create_materialized_view.md
@@ -77,7 +77,7 @@ Optional `WITH` clause options:
 
 |Name|Type| Description                                                                                                                                                                                                                                |Default value|
 |-|-|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-|
-|`timescaledb.chunk_time_interval`|INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.                                                                                                     |
+|`timescaledb.chunk_interval`|INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.                                                                                                     |
 |`timescaledb.create_group_indexes`|BOOLEAN| Create indexes on the continuous aggregate for columns in its `GROUP BY` clause. Indexes are in the form `(<GROUP_BY_COLUMN>, time_bucket)`                                                                                                |`TRUE`|
 |`timescaledb.finalized`|BOOLEAN| In TimescaleDB 2.7 and above, use the new version of continuous aggregates, which stores finalized results for aggregate functions. Supports all aggregate functions, including ones that use `FILTER`, `ORDER BY`, and `DISTINCT` clauses. |`TRUE`|
 |`timescaledb.materialized_only`|BOOLEAN| Return only materialized data when querying the continuous aggregate view                                                                                                                                                                  |`TRUE`|

From fe6b44e5c44e48f95118c5621f7dca742e748891 Mon Sep 17 00:00:00 2001
From: Keyur Panchal <keyur@timescale.com>
Date: Mon, 7 Jul 2025 12:43:32 -0600
Subject: [PATCH 3/3] Specify that parameter was renamed in 2.20

---
 api/continuous-aggregates/alter_materialized_view.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/api/continuous-aggregates/alter_materialized_view.md b/api/continuous-aggregates/alter_materialized_view.md
index e16f364ec5..8dc4053fb3 100644
--- a/api/continuous-aggregates/alter_materialized_view.md
+++ b/api/continuous-aggregates/alter_materialized_view.md
@@ -45,7 +45,7 @@ ALTER MATERIALIZED VIEW <view_name> SET ( timescaledb.<option> =  <value> [, ...
 | `timescaledb.compress_segmentby`           | TEXT                                    | Column list on which to key the compressed segments. An identifier representing the source of the data such as `device_id` or `tags_id` is usually a good candidate. The default is no `segment by` columns.                                                                                                                                                                                                                                       |
 | `timescaledb.compress_chunk_time_interval` | TEXT                                    | EXPERIMENTAL: set compressed chunk time interval used to roll compressed chunks into. This parameter compresses every chunk, and then merges it into a previous adjacent chunk if possible, to reduce the total number of chunks in the hypertable. It should be set to a multiple of the current chunk interval. This option can be changed independently of other compression settings and does not require the `timescaledb.compress` argument. |
 | `timescaledb.enable_cagg_window_functions` | BOOLEAN                                 | EXPERIMENTAL: enable window functions on continuous aggregates. Support is experimental, as there is a risk of data inconsistency if the user is not careful. For example, in backfill scenarios, buckets could be missed. |
-| `timescaledb.chunk_interval`          |INTERVAL| Set the chunk interval. The default value is 10x the original hypertable.  |
+| `timescaledb.chunk_interval` (formerly `timescaledb.chunk_time_interval`)          |INTERVAL| Set the chunk interval. The default value is 10x the original hypertable. Renamed in Timescale 2.20. |
 
 ## Sample usage