- Notifications
You must be signed in to change notification settings - Fork35
[#249] Fix of port number leak in NodeBackup::spawn_replica#250
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
dmitry-lipetsk merged 5 commits intopostgrespro:masterfromdmitry-lipetsk:D20250504_003--releasing_of_portMay 4, 2025
Merged
[#249] Fix of port number leak in NodeBackup::spawn_replica#250
dmitry-lipetsk merged 5 commits intopostgrespro:masterfromdmitry-lipetsk:D20250504_003--releasing_of_portMay 4, 2025
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
We must release a port number after the shutdown and cleanup operation not before.It is a part of work forpostgrespro#249
This private method releases all the allocated node resources (port and so on).PostgresNode::__exit__ calls this new method instead free_port.
…is addedWhen this argument is True, cleanup calls _release_resources method.Default value is False.
…ed port number during failureNodeBackup::spawn_replica uses an explict "rollback" code to destroy a newly allocated node to release a reserved port number.
c3b25b2
intopostgrespro:master 1 check passed
Uh oh!
There was an error while loading.Please reload this page.
Sign up for freeto 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.
Uh oh!
There was an error while loading.Please reload this page.
This patch has the following changes:
It adds a new argument release_resources to PostgresNode::cleanup method. Default value is False.
It fixes a port number leak in NodeBackup::spawn_replica through explicit call of PostgresNode::cleanup(release_resources=True).
Closes#249.