fix: use server-prepared statements for batch inserts when prepareThreshold>0 #841
Conversation
This file contains 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
Codecov Report
@@ Coverage Diff @@
## master #841 +/- ##
============================================
+ Coverage 65.56% 65.57% +0.01%
- Complexity 3545 3548 +3
============================================
Files 166 166
Lines 15250 15252 +2
Branches 2475 2475
============================================
+ Hits 9998 10002 +4
+ Misses 4074 4070 -4
- Partials 1178 1180 +2 |
…eshold>0 Use server-prepared statements when more than 1 row is inserted via executeBatch() API. Previously it could take up to prepareThresolds batch executions. see pgjdbc#836
vlsi
force-pushed
the
server_prepare_on_batch
branch
from
0ef9f61
to
edc7c01
Compare
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.
Use server-prepared statements when more than 1 row is inserted via executeBatch() API.
Previously it could take up to prepareThresolds batch executions.
see #836