Allow database owner to configure hypertables and policies#9668
Open
Allow database owner to configure hypertables and policies#9668
Conversation
The database owner can now run TimescaleDB configuration commands.
Until now only the table or job owner was allowed.
What the database owner can now do:
- Hypertables: set_chunk_time_interval, add_dimension and the
other dimension setters, add and remove a compression,
retention, or reorder policy.
- Continuous aggregates: add and remove the refresh policy.
- Jobs: alter_job, run_job, delete_job.
What still needs the table owner:
ALTER TABLE, ALTER MATERIALIZED VIEW, REINDEX, and CREATE INDEX
on hypertables or continuous aggregates. PostgreSQL checks the
table owner before TimescaleDB sees the command, so the database
owner is rejected upfront.
|
@dbeck, @Poroma-Banerjee: please review this pull request.
|
Member
|
Should the database owner also have visibility into the |
Poroma-Banerjee
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The database owner can now run TimescaleDB configuration commands.
Until now only the table or job owner was allowed.
What the database owner can now do:
other dimension setters, add and remove a compression,
retention, or reorder policy.
What still needs the table owner:
ALTER TABLE, ALTER MATERIALIZED VIEW, REINDEX, and CREATE INDEX
on hypertables or continuous aggregates. PostgreSQL checks the
table owner before TimescaleDB sees the command, so the database
owner is rejected upfront.