Skip to content

Backport to 2.19.x: #7911: Don't create hypertable for published tables #7916

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 5, 2025

Conversation

timescale-automation
Copy link
Member

This is an automated backport of #7911: Don't create hypertable for published tables.
The original issue is #7208.
This PR will be merged automatically after all the relevant CI checks pass. If this fix should not be backported, or will be backported manually, just close this PR. You can use the backport branch to add your changes, it won't be modified automatically anymore.

For more details, please see the documentation

Original description

Don't create hypertable for published tables

Logical Replication of hypertables is not supported (for implementation reasons). We do not allow creation of hypertables
with publications and now throw an error if attempted.

Closes #7208

Logical Replication of hypertables is not supported (for
implementation reasons). We do not allow creation of hypertables
with publications and now throw an error if attempted.

(cherry picked from commit 7173276)
@timescale-automation timescale-automation added the is-auto-backport PR created by backport automation label Apr 4, 2025
@timescale-automation timescale-automation enabled auto-merge (rebase) April 4, 2025 20:45
@timescale-automation timescale-automation merged commit b95c847 into 2.19.x Apr 5, 2025
43 of 44 checks passed
@timescale-automation timescale-automation deleted the backport/2.19.x/7911 branch April 5, 2025 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is-auto-backport PR created by backport automation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants