Improve dump and restore time

Поиск
Список
Период
Сортировка
От Pascal Cohen
Тема Improve dump and restore time
Дата
Msg-id 48EF71F5.5050705@wimba.com
обсуждение исходный текст
Ответы Re: Improve dump and restore time  (Guillaume Lelarge <guillaume@lelarge.info>)
Re: Improve dump and restore time  (Greg Smith <gsmith@gregsmith.com>)
Список pgsql-general
Hello,
I am studying how to migrate our Production Database which is running
under PG 8.2 and we would like to move to PG 8.3
I have read that the only safe solution is to perform a dump and restore.
Our DB is around 6GB large.
I wanted to have an expectation of the migration duration and performed
it on a less powerful machine than the one we have in Production.
Unfortunately it took very very long time (around 27 hours!).
Are there best practices to reduce the migration time ?
Some kind of questions I try to solve:
- Is it better to use a compressed dump or not ?
- Should I use a kind of trick like reading dump file from network while
restoring on the machine to reduce concurrent I/O and so on

Any advice is welcome.

Thanks!

В списке pgsql-general по дате отправления:

Предыдущее
От: "Grzegorz Jaśkiewicz"
Дата:
Сообщение: Re: Using subquery or creating temp table
Следующее
От: Bill Thoen
Дата:
Сообщение: Bug In COPY TO?