Re: Converting 7.x to 8.x

Поиск
Список
Период
Сортировка
Искать
От
Jim Nasby
Тема
Re: Converting 7.x to 8.x
Дата
Msg-id
C68E0D20-42A8-4DFB-B0DA-4463306FAD86@decibel.org
Ответ на
Список
Дерево обсуждения
Converting 7.x to 8.x Carlos <CarlosO@pbsinet.com>
Re: Converting 7.x to 8.x Benjamin Smith <lists@benjamindsmith.com>
Re: Converting 7.x to 8.x Jim Nasby <decibel@decibel.org>
Re: Converting 7.x to 8.x "Anton Melser" <melser.anton@gmail.com>
Re: Converting 7.x to 8.x Ron Johnson <ron.l.johnson@cox.net>
Re: Converting 7.x to 8.x Vivek Khera <vivek@khera.org>
Re: Converting 7.x to 8.x Ron Johnson <ron.l.johnson@cox.net>
Re: Converting 7.x to 8.x Jim Nasby <decibel@decibel.org>
Re: Converting 7.x to 8.x Ron Johnson <ron.l.johnson@cox.net>
Re: Converting 7.x to 8.x Chris <dmagick@gmail.com>
Re: Converting 7.x to 8.x Bruno Wolff III <bruno@wolff.to>
On Jan 27, 2007, at 10:45 AM, Ron Johnson wrote:
> Using slony or "piped pg_dump" requires that you have *double* the
> amount of disk space.  Having a *very large* database and double
> capacity of SCSI disks (including storage controllers, shelves, etc,
> etc) is expensive, and might not be available.

You sure it has to be SCSI?

Even better question... how are you backing up right now? Are you  
ready to accept the huge amount of downtime to restore from backup if  
your server explodes?

In any case, there is an update utility for 8.1->8.2... you could  
look into hacking that to work for 7.4->8.*.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)


В списке pgsql-general по дате отправления
От: Jim Nasby
Дата:
Сообщение: Re: SQL Newbie Question
От: Jim Nasby
Дата:
Сообщение: Re: Index bloat of 4x
FAQ