Skip to content
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

Disallow MergeAppend optimizations when there is an OSM chunk #5519

Merged

Conversation

zilder
Copy link
Contributor

@zilder zilder commented Apr 3, 2023

OSM chunks have their own fdw_private which conflicts with checks in the MergeAppend code path causing segfaults. This PR fixes this by returning early when there is an OSM chunk in the MergeAppendPath.

OSM chunks have their own fdw_private which conflicts with checks in
the MergeAppend code path causing segfaults. This commit fixes this by
returning early when there is an OSM chunk in the MergeAppendPath.
@github-actions
Copy link

github-actions bot commented Apr 3, 2023

@konskov, @erimatnor: please review this pull request.

Powered by pull-review

@codecov
Copy link

codecov bot commented Apr 3, 2023

Codecov Report

Merging #5519 (04c903b) into main (517dee9) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #5519      +/-   ##
==========================================
- Coverage   90.89%   90.75%   -0.15%     
==========================================
  Files         228      229       +1     
  Lines       46192    53700    +7508     
==========================================
+ Hits        41987    48734    +6747     
- Misses       4205     4966     +761     
Impacted Files Coverage Δ
src/planner/planner.c 95.98% <100.00%> (+0.20%) ⬆️

... and 205 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@zilder zilder merged commit c6b9f50 into timescale:main Apr 3, 2023
39 of 41 checks passed
@gayyappan gayyappan added this to the TimescaleDB 2.10.2 milestone Apr 3, 2023
@akuzm akuzm added the force-auto-backport Automatically backport this PR or fix of this issue, even if it's not marked as "bug" label Apr 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backported-2.10.x force-auto-backport Automatically backport this PR or fix of this issue, even if it's not marked as "bug"
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants