You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the dump:load command just does not the target database structure at all. This is quite bad when it comes to a real backup load with a different migration state. It's not enough to clear and reimport all the data.
The the dump creation MUST take care of including the whole schema and the load command MUST take care of dropping the database first, recreate it, load the schema and then the data from the dump.
Looks like pg_restore is not able to this by passing --clean and --create together, due to:
When this option is used, the database named with -d is used only to issue the initial DROP DATABASE and CREATE DATABASE commands. All data is restored into the database name that appears in the archive.
So we should drop+create the database first, with a psql statement.
--
I will come up with a PR for this soon. :)
The text was updated successfully, but these errors were encountered:
Currently the
dump:load
command just does not the target database structure at all. This is quite bad when it comes to a real backup load with a different migration state. It's not enough to clear and reimport all the data.The the dump creation MUST take care of including the whole schema and the load command MUST take care of dropping the database first, recreate it, load the schema and then the data from the dump.
Looks like pg_restore is not able to this by passing
--clean
and--create
together, due to:So we should drop+create the database first, with a psql statement.
--
I will come up with a PR for this soon. :)
The text was updated successfully, but these errors were encountered: