seen from Germany
seen from Türkiye
seen from United States
seen from Germany
seen from United States
seen from Australia
seen from Belgium
seen from United States
seen from Saudi Arabia
seen from United States
seen from Türkiye
seen from Malaysia
seen from China
seen from China
seen from Bangladesh
seen from United States
seen from Canada
seen from United States
seen from Russia
seen from United States
db:drop, pg_restore
do in this order:
delete from migration_schema rake db:drop rake db:create rake db:migrate pg_restore --verbose -a --no-acl --no-owner -h localhost -d libval_development ~/Desktop/20150311.dump
UPDATE: only using pg_restore obviously doesn't work on existing db; if you don't care about existing data:
sudo -u postgres pg_restore --create --clean -d postgres /path/to/dbbackup.sql
doesnt work on mbp
http://dba.stackexchange.com/a/66705
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
pg_restore stuck on create materialized view
http://postgresql.nabble.com/Failure-loading-materialized-view-with-pg-restore-td5838393.html
pg_restore --verbose -a --no-acl --no-owner -h localhost -d libval_development ~/Desktop/20150311.dump
the -a means only restore data
used pg_dumpall -s to see log of the process
this didn't work; my schema had been changed, and an association didn't work (couldn't find primary key of a particular table). so i'm doing a full clean restore again. it's stuck on matviews again at 15 min so far. don't know how long i should give it.
