Skip to content
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

message body size limits in frontend and backend #2139

Closed
zenkovev opened this issue Oct 2, 2024 · 0 comments
Closed

message body size limits in frontend and backend #2139

zenkovev opened this issue Oct 2, 2024 · 0 comments

Comments

@zenkovev
Copy link
Contributor

zenkovev commented Oct 2, 2024

Hello, I would like to suggest a little more control over the maximum message length, implemented here. #1836. Firstly, previous fix does not take into account the possibility of receiving messages with an incorrect specified length from the server, and secondly, using the method for Frontend and Backend messages will not allow them to be applied to the use of the pgx library.
I propose a PR that solves these two problems. #2138.
Note: The problem is not abstract and is reproduced in practice. Specifically, when updating the major version of the postgres in Spilo (used in Postgres Operator), rsync is launched on port 5432, which responds with messages prefixed with @RSYN. The library interprets this as a message with a length of 1381194062 and allocates a buffer of about 1GB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant