[postgrenosql] Each thread gets its own connection to the database. #1691
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.
While the PostgreSQL JDBC driver is thread-safe
(ref), multiple threads using the same connection returned from the driver will still block each other.
This change updates the DB client implementation to have each thread maintain their own driver and connection. This is useful in the transaction phase to improve the throughput performance of a single load driver process without having to resort to using multiple processes.