add info about 5.0 version of create-standby #6985
Merged
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
|
If anyone thinks it's helpful, I could also add a link here to the 5.1 release notes that say the privilege is no longer required, but that's sorta just repeating information. |
EFM-Bobby
added
the
deploy
In 5.0 when the 'efm create-standby' command was introduced, it required superuser privileges to run since it needed to be able to start the db as a service without using the normal efm scripts. In 5.1 this was fixed so that it can be run as the 'efm' user, and the documentation was changed to remove the requirement text, but people will still get caught up on this if using 5.0.
gvasquezvargas
force-pushed
the
EFM-5_0-specific-privilege-requirement
branch
from
fc7a569 to
d558d5c
Compare
Sign up for free
to 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.
In 5.0 when the 'efm create-standby' command was introduced, it required superuser privileges to run since it needed to be able to start the db as a service without using the normal efm scripts. In 5.1 this was fixed so that it can be run as the 'efm' user, and the documentation was changed to remove the requirement text, but people will still get caught up on this if using 5.0.
What Changed?