fix: reset public schema before restore pg_dump #20
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
ShockwaveNN
requested review from
VitaliySerov
and removed request for
ShockwaveNN
VitaliySerov
approved these changes
Mar 11, 2024
askonev
force-pushed
the
feature/restore_backup
branch
3 times, most recently
from
f659db4
to
e8e6fac
Compare
VitaliySerov
requested changes
Mar 14, 2024
askonev
force-pushed
the
feature/restore_backup
branch
from
e8e6fac
to
c1d91d6
Compare
VitaliySerov
approved these changes
Mar 15, 2024
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.
I ran into a problem: When restoring the database dump, some of the data was not restored due to an error:
Table already existsI propose to cascade droped the public scheme as a temporary solution. And then restore access rights