fix error when db persistence enabled (#57) #58
Merged
Conversation
This file contains 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
arpagon
approved these changes
Apr 26, 2024
@arpagon We might need to update |
badgifter
pushed a commit
to badgifter/supabase-helm
that referenced
this pull request
May 30, 2024
fix error when db persistence enabled (supabase-community#57)
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.
What kind of change does this PR introduce?
bug fix
What is the current behavior?
fixes "initdb: error: directory "/var/lib/postgresql/data" exists but is not empty" errors when db persistence is enabled (#57)
What is the new behavior?
successful initialisation of the database
Additional context
Add any other context or screenshots.