fix: Add explicit parameters limit in PostgreSQL and Redshift drivers #8784
+76
−1
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.
Check List
Description of Changes Made (if issue reference is not provided)
PostgresDriver
usespg
module as a driver, andpg
does not check incoming params, and if there's too many it just sends incorrect bind message. It would end up as "expected a lot of params, but 0 was passed" error from server.RedshiftDriver
extendsPostgresDriver
, but there's another catch: Redshift server misbehaves a little, and breaks on 32768 or more parameters withthere is no parameter $-32768
.There's not much we can do about it, but at least we can make error messages clear.