[#329] get_pg_node_state looks for postmaster to avoid "PID file is empty" error#4
Closed
dmitry-lipetsk wants to merge 4 commits intomasterfrom
Closed
[#329] get_pg_node_state looks for postmaster to avoid "PID file is empty" error#4dmitry-lipetsk wants to merge 4 commits intomasterfrom
dmitry-lipetsk wants to merge 4 commits intomasterfrom
Conversation
…D file is empty" error This patch suggests a solution to fix an error "PID file is empty" during getting a server state data. When pg_ctl returns this error, we are trying to find postmaster process for our data directory. If we find it then we wait a few seconds and do the next attempt to get server state data. Closes postgrespro#329.
Owner
Author
|
OK |
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
1 participant
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.
This patch suggests a solution to fix an error "PID file is empty" during getting a server state data.
When pg_ctl returns this error, we are trying to find postmaster process for our data directory.
If we find it then we wait a few seconds and do the next attempt to get a server state data.
Closes postgrespro#329.