-
Notifications
You must be signed in to change notification settings - Fork 897
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
[Enhancement]: Replica identity full on hypertables with enabled compression #6158
Comments
This unblocks the execution of `ALTER TABLE ... REPLICA IDENTITY ...` on hypertables with compression enabled. The configured replica identity only propagates to tables belonging to the uncompressed hypertable. Fixes: #6158
This unblocks the execution of `ALTER TABLE ... REPLICA IDENTITY ...` on hypertables with compression enabled. The configured replica identity only propagates to tables belonging to the uncompressed hypertable. Fixes: #6158
This unblocks the execution of `ALTER TABLE ... REPLICA IDENTITY ...` on hypertables with compression enabled. The configured replica identity only propagates to tables belonging to the uncompressed hypertable. Fixes: #6158
This unblocks the execution of `ALTER TABLE ... REPLICA IDENTITY ...` on hypertables with compression enabled. The configured replica identity only propagates to tables belonging to the uncompressed hypertable. Fixes: #6158
@flexwende We've unblocked the This should be part of the TimescaleDB 2.16 release. I don't know when it will be released, but probably in a few months. |
What type of enhancement is this?
API improvement
What subsystems and features will be improved?
Compression
What does the enhancement do?
Similar to the latest additions in release 2.12.0 (#6086) and the pull requests #5868 and #5515, make hypertables, that have compression enabled, also support replica identity full.
The current state (2.12.0, postgres 15) is:
Is that generally possible at all with the compressed data structure?
If so, is implementation planned?
Implementation challenges
No response
The text was updated successfully, but these errors were encountered: