Skip to content

Improved port number management #164

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.

Sign up for GitHub

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

Jump to bottom
Closed
dmitry-lipetsk opened this issue Dec 12, 2024 · 0 comments
Closed

Improved port number management #164

dmitry-lipetsk opened this issue Dec 12, 2024 · 0 comments

Comments

@dmitry-lipetsk
Copy link
Collaborator

It is needed to improve the port number management code - reserving and releasing.

For example, we must not try to reassign a port number that was defined by client when we get a conflict during start of node.
dmitry-lipetsk added a commit to dmitry-lipetsk/testgres that referenced this issue Dec 12, 2024
@dmitry-lipetsk
Port numbers management is improved (postgrespro#164)
28ac425 
- We don't release a port number that was defined by client
- We only check log files to detect port number conflicts
- We use slightly smarter log file checking

A test is added.
@dmitry-lipetsk dmitry-lipetsk mentioned this issue Dec 12, 2024
Merged
dmitry-lipetsk added a commit that referenced this issue Dec 15, 2024
@dmitry-lipetsk
Merge pull request #165 from dmitry-lipetsk/master-fix164--v01
69b35cb 
Port numbers management is improved (#164)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dmitry-lipetsk