Re: db not dumping properly, or at least not restoring

Поиск
Список
Период
Сортировка
От Kirk Wythers
Тема Re: db not dumping properly, or at least not restoring
Дата
Msg-id 284DE886-3C56-483E-99F4-E1CA8CDE7D3B@umn.edu
обсуждение исходный текст
Ответ на Re: db not dumping properly, or at least not restoring  (Scott Marlowe <scott.marlowe@gmail.com>)
Ответы Re: db not dumping properly, or at least not restoring  (Scott Marlowe <scott.marlowe@gmail.com>)
Список pgsql-general
On Oct 16, 2009, at 4:51 PM, Scott Marlowe <scott.marlowe@gmail.com>
wrote:

> On Fri, Oct 16, 2009 at 11:25 AM, Kirk Wythers <kwythers@umn.edu>
> wrote:
>
>> Any ideas what the problem could be here?
>
> Use the pg_dump from the target (i.e. newer) pgsql.  I.e. if going
> from 8.3.8 to 8.4.1, use the pg_dump that comes with 8.4.1 to dump the
> 8.3.8 database.
>
Can I assume that this is even more critical if gong from 8.2 to 8.4?


> I usually just do it like so:
>
> (First migrate accounts:)
> pg_dumpall --globals -h oldserver | psql -h newserver postgres

I'm a little confused here. Are you saying to used the network
connections between thetwo servers and to pipe the dumpall directly to
the psql load?

> (then each database:)
> createdb -h newserver dbname

Then create new databases on the the new server to match the. The
names from the old server?


> pg_dump -h oldserver dbname | psql -h newserver dbname
> (repeat as needed, save output for error messages)

Then dump each database individually and pipe the dump to the psql load?


These two procedures seem to duplicate the goal? Or am I mosaic
something?

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

Предыдущее
От: Dennis Gearon
Дата:
Сообщение: pgadmin3 hangs during dump
Следующее
От: Greg Stark
Дата:
Сообщение: Re: contrib/plantuner - enable PostgreSQL planner hints