From: | "guillermo schulman" <gsmiscel(at)hotmail(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Backup method and vacuumdb |
Date: | 2003-02-13 12:20:13 |
Message-ID: | F36EEmYDKFJ2I13pL320001d2d4@hotmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
I'm doing some migration script from mysql database to an existing
postgresql database. Everytime I want to test it, I want to get the postgres
"destination" database to the same situation it was before the last script
was run.
I am doing a backup with pgdump and restoring by droping the database and
running the script generated by pgdump.
The backup looks like this:
pg_dump -h <hostname> -U <username> -c dbname > /tmp/database.pgdump
The restore looks like this:
psql -h <hostname> -U <username> template1 -c "drop database dbname;"
psql -h <hostname> -U <username> template1 < /tmp/database.pgdump
But this aproach is taking a long time and the database is becoming slower
every time.
So: which is the best backup/restore method to apply in this case? And about
the performance, I'm using vacuumdb but I don't know when to do it. Any
idea?
Thanks
_________________________________________________________________
Charla con tus amigos en línea mediante MSN Messenger:
http://messenger.yupimsn.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Clucas | 2003-02-13 12:27:36 | Cygwin and C triggers |
Previous Message | Oliver Elphick | 2003-02-13 11:28:42 | Re: view users |