Re: Resurrecting pg_upgrade

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Resurrecting pg_upgrade
Дата
Msg-id 22350.1071266186@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Resurrecting pg_upgrade  (Dave Smith <dave.smith@candata.com>)
Ответы Re: Resurrecting pg_upgrade  (Thomas Swan <tswan@idigx.com>)
Список pgsql-hackers
Dave Smith <dave.smith@candata.com> writes:
> Why not go the other way. 
> 1) Dump the schemas.
> 2) Initdb with the new schemas in a tmp PGDATA
> 3) backup the schemas in the current PGDATA
> 4) move the new schemas from the new db into the current one.

This seems like approximately the same thing except you lose the
property of not having modified the old DB if you fail partway through.
What's the advantage exactly?

> This means that doing an update you would only have to have space for
> the system catalogs  not the whole database. 

That's true either way.
        regards, tom lane


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

Предыдущее
От: Dave Smith
Дата:
Сообщение: Re: Resurrecting pg_upgrade
Следующее
От: markw@osdl.org
Дата:
Сообщение: more dbt-2 results hyperthreading on linux-2.6.0-test11