By using pg_dumpall instead of pg_dump we ensure that ALL resources of the database are being exported in the backup file, which is now an SQL script instead of .dump due to the nature of pg_dumpall. This means that previous issues are now resolved, i.e.
Missing privileges
Missing roles
We also migated from pg_restore to the standard psql command, running it in the format of,
psql -h <address> -U <user> -p <port> -f <SQL script>
This, with the addition of pg_dumpall solves our major issue of being unable to run pg_restore on an already "restored" database.
By using
pg_dumpallinstead ofpg_dumpwe ensure that ALL resources of the database are being exported in the backup file, which is now an SQL script instead of.dumpdue to the nature ofpg_dumpall. This means that previous issues are now resolved, i.e.We also migated from
pg_restoreto the standardpsqlcommand, running it in the format of,psql -h <address> -U <user> -p <port> -f <SQL script>This, with the addition of
pg_dumpallsolves our major issue of being unable to runpg_restoreon an already "restored" database.