Skip to content

Commit 8023696

Browse files
committed
Fix outdated claim that continuous aggregate schemas can't change
TimescaleDB 2.28.0 (timescale/timescaledb#9825) adds ADD COLUMN on continuous aggregates, so the note stating no schema changes are possible is no longer accurate. Point it at the ALTER MATERIALIZED VIEW reference.
1 parent 074e5e7 commit 8023696

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

src/content/docs/build/performance-optimization/alter-update-table-schema.mdx

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,11 @@ Schema changes on a {C.HYPERTABLE} use normal {C.PG} `ALTER TABLE` syntax, and {
1212

1313
<Callout variant="note">
1414

15-
While you can change the schema of an existing {C.HYPERTABLE}, you cannot change
16-
the schema of a {C.CAGG}. For {C.CAGG}s, the only
17-
permissible changes are renaming a view, setting a schema, changing the owner,
18-
and adjusting other parameters.
15+
Schema changes to a {C.CAGG} are limited. You can rename the view or its
16+
columns, set a schema, change the owner, and adjust parameters. Since
17+
{C.TIMESCALE_DB} 2.28.0, you can also add a new aggregate with
18+
[`ALTER MATERIALIZED VIEW ... ADD COLUMN`](/reference/timescaledb/continuous-aggregates/alter_materialized_view).
19+
Other schema changes are not supported.
1920

2021
</Callout>
2122

0 commit comments

Comments
 (0)