-
Notifications
You must be signed in to change notification settings - Fork 898
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
Fix UPSERT with prepared statements #1196
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1196 +/- ##
========================================
Coverage ? 92.4%
========================================
Files ? 107
Lines ? 13689
Branches ? 0
========================================
Hits ? 12650
Misses ? 1039
Partials ? 0
Continue to review full report at Codecov.
|
84eeba1
to
33ed1b7
Compare
c5533d0
to
f137edd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great. One outdated comment to fix before merge.
@@ -158,17 +158,6 @@ chunk_dispatch_end(CustomScanState *node) | |||
ExecEndNode(substate); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a now-outdated comment at line 245 of this file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
starts with "Save arbiterIndexes..."
When doing upsert with prepared statement the code to restore arbiter_indexes would not trigger when an error occurred on the INSERT leading to a segfault on the next EXECUTE of the prepared statement.
When doing upsert with prepared statement the code to restore
arbiter_indexes would not trigger when an error occurred on the
INSERT leading to a segfault on the next EXECUTE of the prepared
statement.
Fixes #1165