Skip to content

Port numbers management is improved (#164) #165

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

Merged
merged 6 commits into from
Dec 15, 2024

Conversation

dmitry-lipetsk
Copy link
Collaborator

This PR improves a managemenet of port numbers.

  • 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.

This patch closes the issue #164.

…numbers management.

This need to replace port numbers management in unit tests.
It is a specialized function to read binary data from files.
It is a function to get a size of file.
- 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 changed the title [Port numbers management is improved (#164) Dec 12, 2024
Also
- TestgresTests.test_the_same_port is updated
- TestgresTests.test_port_rereserve_during_node_start is updated
- TestgresTests.test_port_conflict is added
@dmitry-lipetsk dmitry-lipetsk merged commit 69b35cb into postgrespro:master Dec 15, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants