PostgresNode::is_started is read-only and is not used internally#305
Merged
dmitry-lipetsk merged 4 commits intopostgrespro:masterfrom Jan 8, 2026
Merged
Conversation
PostgresNode::is_started provides information about a manually started node. It is "set" in start method and is reset in stop, kill methods. These methods do not verify this flag. So we cannot stop and start our node twice. An updated implementation of kill method raises InvalidOperationException when our node is not running.
dmitry-lipetsk
changed the title
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.
PostgresNode::is_started provides information about a manually started node.
It is "set" in start method and is "reset" in stop, kill methods.
These methods do not verify this flag and do not use for other aims - for example to ignore the second start or stop of a node.
So we cannot stop and start our node twice.
An updated implementation of kill method raises InvalidOperationException when our node is not running.
This patch allows to use testgres in code where a node started or stopped explicitly, not via start/stop/kill methods.