Fix PG_ErrorInfo and ER_ReturnError when error message is larger than 65535 bytes#70
Merged
davecramer merged 1 commit intopostgresql-interfaces:mainfrom Nov 3, 2024
Merged
Conversation
Contributor
|
Interesting. Did you run into this in a real situation ? |
Contributor
Author
|
Yes, but I was not connecting to Postgres, but another database that gives a very long error message. |
This file contains hidden or 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
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.
Old driver truncated the server error message incorrectly.
old implementation
environ.c:147:
When
errsizeis larger than 32767, the errorsize is wrong.environ.c:204:
msglenis truncated when msg is larger than 65535 bytes.environ.c:224:
errorposis used but never set.new implementaion
In
PG_ErrorInfo, makeserrsize,errposUInt4.Fix
ER_ConstructandER_Dup.In
ER_ReturnError, makesmsglen,wrtlen,pcblenUInt4, and seterrposcorrectly.