Defer initialization of child plan states in ModifyHypertable node - #9952
Merged
Conversation
The underlying scans must be initialized after we decompress the data potentially affected by DML operations, so that the scans see this data. At the moment we're restarting the scans after decompression, but this is not the proper Postgres protocol, so it breaks.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
akuzm
marked this pull request as ready for review
June 10, 2026 11:46
|
@Poroma-Banerjee, @dbeck: please review this pull request.
|
dbeck
approved these changes
Jun 12, 2026
antekresic
approved these changes
Jun 18, 2026
antekresic
left a comment
Member
There was a problem hiding this comment.
Great improvement, glad to have the workaround removed 🎉
natalya-aksman
approved these changes
Jun 18, 2026
Member
|
Automated backport to 2.28.x not done: cherry-pick failed. Git status |
akuzm
added a commit
to akuzm/timescaledb
that referenced
this pull request
Jun 22, 2026
…imescale#9952) The underlying scans must be initialized after we decompress the data potentially affected by DML operations, so that the scans see this data. At the moment we're restarting the scans after decompression, but this is not the proper Postgres protocol, so it breaks. Fixes timescale#9913 (cherry picked from commit 9636ef2)
akuzm
added a commit
that referenced
this pull request
Jun 22, 2026
…9952) The underlying scans must be initialized after we decompress the data potentially affected by DML operations, so that the scans see this data. At the moment we're restarting the scans after decompression, but this is not the proper Postgres protocol, so it breaks. Fixes #9913 (cherry picked from commit 9636ef2)
kpan2034
pushed a commit
to kpan2034/timescaledb
that referenced
this pull request
Jul 1, 2026
…imescale#9952) The underlying scans must be initialized after we decompress the data potentially affected by DML operations, so that the scans see this data. At the moment we're restarting the scans after decompression, but this is not the proper Postgres protocol, so it breaks. Fixes timescale#9913
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
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 underlying scans must be initialized after we decompress the data potentially affected by DML operations, so that the scans see this data. At the moment we're restarting the scans after decompression, but this is not the proper Postgres protocol, so it breaks.
Fixes #9913