X-Original-To: pgsql-novice-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B3A213A9E4C; Tue, 21 Dec 2004 07:08:12 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 54337-04; Tue, 21 Dec 2004 07:08:01 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 152193A95C3; Tue, 21 Dec 2004 07:07:59 +0000 (GMT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id iBL77rZ29096; Tue, 21 Dec 2004 16:07:53 +0900 Message-ID: <006b01c4e72c$161775b0$7201a8c0@mst1x5r347kymb> From: "Iain" To: "sarlav kumar" , "pgsqlnovice" , "pgsqlperform" References: <20041220144034.93247.qmail@web51306.mail.yahoo.com> Subject: Re: [PERFORM] Postgres version change - pg_dump Date: Tue, 21 Dec 2004 16:09:55 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0067_01C4E777.8291BC50" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.048 tagged_above=0 required=5 tests=AWL, HTML_50_60, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200412/247 X-Sequence-Number: 11824 This is a multi-part message in MIME format. ------=_NextPart_000_0067_01C4E777.8291BC50 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit 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 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. regards Iain ----- Original Message ----- From: sarlav kumar To: pgsqlnovice ; pgsqlperform 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. version ------------------------------------------------------------- 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. version ------------------------------------------------------------------------------------------------------------------------- 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, Saranya ------------------------------------------------------------------------------ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. Learn more. ------=_NextPart_000_0067_01C4E777.8291BC50 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
As others have already said, = use the newer=20 version of pg_dump and it should go ok.
 
I had lots of problems = restoring 7.1 dumps=20 into 7.4 database, but it goes smoothly if I use the 7.4 version of=20 pg_dump.
 
Assuming you have 2 servers, = the old one=20 and a new one, call pg_dump from your new server as = follows:
 
pg_dump --username=3Dpostgres=20 --host=3D192.168.x,x  <other options>
 
and use the IP address of the = old server=20 for the --host parameter.
 
You may need to edit the = pg_hba.conf file=20 on the old server to allow the connection from the new = server.
 
This is pretty convenient as = you don't=20 even have to copy the dump file from the old server.
 
I was thinking you could = set up a=20 backup server in this way. On a busy system, it may take a load of the = main=20 server so that running backups with users online shouldn't be a problem. = That's=20 in theory anyway.
 
regards
Iain
 
----- Original Message ----- =
From:=20 sarlav = kumar=20
To: pgsqlnovice ; pgsqlperform =
Sent: Monday, December = 20, 2004=20 11:40 PM
Subject: [PERFORM] = Postgres=20 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.
 
=
 version         &= nbsp;           &n= bsp;    =20 =
-------------------------------------------------------------
&nbs= p;PostgreSQL=20 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=20 the Fedora Core 3 package installed.
 
=
version          &= nbsp;           &n= bsp;           &nb= sp;           &nbs= p;         =20 =
---------------------------------------------------------------------= ----------------------------------------------------
 PostgreSQL = 7.4.6 on i386-redhat-linux-gnu, compiled by GCC i386-redhat-linux-gcc = (GCC)=20 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=20 new database on Postgres 7.4.6. I would like to know if there would be = any=20 problem due to the postgres version/OS change. If so, could someone = tell me=20 what precautions I can take to avoid any problems?
 
Thanks in advance,
Saranya
 
 
 


Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced = search.=20 Learn=20 more. ------=_NextPart_000_0067_01C4E777.8291BC50--