Fixed hub install when PostgreSQL data or backup directory is a mount point - #2388
Open
nickanderson wants to merge 1 commit into
Open
Fixed hub install when PostgreSQL data or backup directory is a mount point#2388nickanderson wants to merge 1 commit into
nickanderson wants to merge 1 commit into
Conversation
… point `rm -rf` cannot remove a mount point even after emptying it, and the package scripts treated that non-zero exit as failure. They now check whether the directory ended up empty instead, run initdb via a staging directory when nested mounts such as a separate pg_wal volume survive, and tolerate lost+found in BACKUP_DIR. Ticket: ENT-14392 Changelog: title
nickanderson
force-pushed
the
ENT-14392/master
branch
2 times, most recently
from
July 30, 2026 22:00
f429472 to
9d95bc0
Compare
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.
rm -rfcannot remove a mount point even after emptying it, and the packagescripts treated that non-zero exit as failure. They now check whether the
directory ended up empty instead, run initdb via a staging directory when
nested mounts such as a separate pg_wal volume survive, and tolerate
lost+found in BACKUP_DIR.
Ticket: ENT-14392
Changelog: title