Skip to content

Document ADD COLUMN on continuous aggregates (2.28.0) - #316

Merged
atovpeko merged 4 commits into
atovpeko1/edu-136-timescale-db-228-releasefrom
atovpeko1/edu-136-cagg-add-column
Jun 12, 2026
Merged

Document ADD COLUMN on continuous aggregates (2.28.0)#316
atovpeko merged 4 commits into
atovpeko1/edu-136-timescale-db-228-releasefrom
atovpeko1/edu-136-cagg-add-column

Conversation

@atovpeko

@atovpeko atovpeko commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Describe your changes

Documents ALTER MATERIALIZED VIEW <cagg> ADD COLUMN <name> <type> GENERATED ALWAYS AS (<aggregate>) STORED, added in TimescaleDB 2.28.0 (timescale/timescaledb#9825), on the continuous aggregate ALTER MATERIALIZED VIEW reference page.

  • Adds the clause to the supported-clauses list, with a note that new data populates the column going forward and existing rows stay NULL until a forced refresh backfills them.
  • Reframes the list lead-in so it no longer implies every bullet is a standard PostgreSQL ALTER VIEW clause: aggregates in generated columns are TimescaleDB-specific and not valid in plain PostgreSQL.

Affected pages

Related Issues

Issue: https://linear.app/tigerdata/issue/EDU-136

Checklist before requesting a review

  • - This is ready for review. If not, raise as a draft PR
  • - I have reviewed my changes.
  • - I have confirmed the content is technically accurate.
  • - I have tested any code that is added or updated on the latest available version.
  • - I have confirmed the content is free of typos or grammar errors.
  • - I have verified all images and videos are clear and match production (or dev for unreleased features).
  • - This references a feature that is public. If not, add a note and we can schedule the merge for after the feature release.

TimescaleDB 2.28.0 (timescale/timescaledb#9825) supports adding a new
aggregate to a continuous aggregate in place via ALTER MATERIALIZED
VIEW ADD COLUMN ... GENERATED ALWAYS AS (<aggregate>) STORED.

Reword the clause-list lead-in so it no longer implies every bullet is
a standard PostgreSQL ALTER VIEW clause: aggregates in generated
columns are TimescaleDB-specific and not valid in plain PostgreSQL.
@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tiger-data-docs Ready Ready Preview, Comment Jun 12, 2026 9:59am

… page

Match the page's Samples section, which gives an example for each
supported clause (verified against TimescaleDB 2.28.0).
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.
- Generalize the clause to cover aggregates and GROUP BY columns
- Add a GROUP BY-column example
- Explain NULL-until-backfill behavior and show force => true refresh

Verified against a local 2.29.0-dev build.
@atovpeko
atovpeko merged commit db1d118 into atovpeko1/edu-136-timescale-db-228-release Jun 12, 2026
6 of 8 checks passed
@atovpeko
atovpeko deleted the atovpeko1/edu-136-cagg-add-column branch June 12, 2026 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants