0
Considering your dumped DB file is of ~550MB, I think using the Amazon guide for doing this is the way out. I hope it helps.
0
I think it did not halt. It was just recreating indexes, foreign keys etc. Use pg_restore -v to see what’s going on during the restore. Check the logs or redirect output to a file to check for any errors after import, as this is verbose.
Also I’d recommend using directory format (pg_dump -v -Fd) as it allows for parallel restore (pg_restore -v -j4).
You can ignore this ERROR: must be owner of extension plpgsql. This is only setting a comment on extension, which is installed by default anyway. This is caused by a peculiarity in RDS flavor of PostgreSQL, which does not allow to restore a database while connecting as postgres user.
- [Django]-Django mssql setup : error initializing DB
- [Django]-Segmentation fault (core dumped) with django-storages
- [Django]-CSS missing from django admin pages on development server after execution of drop database
- [Django]-How to truncate content for Mdeditor (content as markdownx) – Django