Re: Postgres version change - pg_dump

From: Stefan Weiss
Subject: Re: Postgres version change - pg_dump
Date: ,
Msg-id: 41C706E3.5040302@foo.at
(view: Whole thread, Raw)
In response to: Postgres version change - pg_dump  (sarlav kumar)
Responses: Re: Postgres version change - pg_dump  (sarlav kumar)
List: pgsql-performance

Tree view

Postgres version change - pg_dump  (sarlav kumar, )
 Re: Postgres version change - pg_dump  (Bruno Wolff III, )
  Re: Postgres version change - pg_dump  (sarlav kumar, )
   Re: Postgres version change - pg_dump  (Christopher Kings-Lynne, )
 Re: Postgres version change - pg_dump  (Stefan Weiss, )
  Re: Postgres version change - pg_dump  (sarlav kumar, )
 Re: Postgres version change - pg_dump  ("Iain", )

sarlav kumar wrote, On 2004-12-20 15:40:
> I would like to do a pg_dump on the test database, and restore it in
> the new database on Postgres 7.4.6. I would like to know if there
> would be any problem due to the postgres version/OS change. If so,
> could someone tell me what precautions I can take to avoid any
> problems?

Apart from using the pg_dump from 7.4.6 (see Bruno's answer), you should
take care to use the same locale in the new database cluster. I have had
problems in the past with unique constraints that could not be restored
due to different locale settings. See here:

  http://www.spinics.net/lists/pgsql/msg05363.html

In my case it was not enough to create the database with a different
encoding, I had to re-initdb the whole cluster :-/


cheers,
stefan


pgsql-performance by date:

From: Theo Galanakis
Date:
Subject: Re: PG Logging is Slow
From: Alexander Borkowski
Date:
Subject: Re: PG Logging is Slow