As others have already said, use the newer version of pg_dump and it should go ok.
I had lots of problems restoring 7.1 dumps into 7.4 database, but it goes smoothly if I use the 7.4 version of pg_dump.
Assuming you have 2 servers, the old one and a new one, call pg_dump from your new server as follows:
pg_dump --username=postgres --host=192.168.x,x  <other options>
and use the IP address of the old server for the --host parameter.
You may need to edit the pg_hba.conf file on the old server to allow the connection from the new server.
This is pretty convenient as you don't even have to copy the dump file from the old server.
I was thinking you could set up a backup server in this way. On a busy system, it may take a load of the main server so that running backups with users online shouldn't be a problem. That's in theory anyway.
----- Original Message -----
Sent: Monday, December 20, 2004 11:40 PM
Subject: [PERFORM] Postgres version change - pg_dump

Hi All,
Thanks to everyone for helping with my previous questions.
I have a test database running on Postgres 7.3.2.
 PostgreSQL 7.3.2 on i686-pc-linux-gnu, compiled by GCC 2.96
I have another server where a newer version of postgres that came with the Fedora Core 3 package installed.
 PostgreSQL 7.4.6 on i386-redhat-linux-gnu, compiled by GCC i386-redhat-linux-gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6)
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?
Thanks in advance,

Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search. Learn more.

Reply via email to