Migration from 7.4.2 to 8.1.4
am 21.08.2006 11:43:28 von gallaij
This is a multi-part message in MIME format.
------=_NextPart_000_0005_01C6C517.04C978B0
Content-Type: text/plain;
charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Hi!
I'm an administrator of a big company who has a PgSQL-database version =
7.4.2. We would like to upgrade it to 8.1.4 but the dump we made cannot =
be restored. We got a lot of error messages while restoring database =
related on something's being restored before other objects would exists. =
( ??? ) We have made some changes in the dump reversing creation =
processes and it seems to be useful but there's a lot of error messages =
on the same problem and do not have time to do them all by hand.
We need help to convert this dump for us ( I can provide binary data if =
needed ) to be able use it with the new system. We would pay this =
conversion.
Thanks in advance,
John Gallai,
System administrator
Mediagnost Ltd,
Budapest,
Hungary
------=_NextPart_000_0005_01C6C517.04C978B0
Content-Type: text/html;
charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
charset=3Diso-8859-2">
Hi!
I'm an administrator of a big company =
who has a=20
PgSQL-database version 7.4.2. We would like to upgrade it to 8.1.4 but =
the=20
dump we made cannot be restored. We got a lot of error =
messages while=20
restoring database related on something's being restored before other =
objects=20
would exists. ( ??? ) We have made some changes in the dump =
reversing=20
creation processes and it seems to be useful but there's a lot of error =
messages=20
on the same problem and do not have time to do them all by=20
hand.
We need help to convert this dump =
for us=20
( I can provide binary data if needed ) to be able =
use it=20
with the new system. We would pay this conversion.
Thanks in advance,
John Gallai,
System administrator
Mediagnost Ltd,
Budapest,
Hungary
------=_NextPart_000_0005_01C6C517.04C978B0--
Re: Migration from 7.4.2 to 8.1.4
am 21.08.2006 14:40:28 von Michael Fuhr
On Mon, Aug 21, 2006 at 11:43:28AM +0200, Gallai J=E1nos wrote:
> I'm an administrator of a big company who has a PgSQL-database
> version 7.4.2. We would like to upgrade it to 8.1.4 but the dump
> we made cannot be restored.
Which version of pg_dump/pg_dumpall did you use? When upgrading
use the newer version (i.e., use 8.1.4's pg_dump against the 7.4.2
database).
--=20
Michael Fuhr
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Re: Migration from 7.4.2 to 8.1.4
am 21.08.2006 14:47:23 von Peter Eisentraut
Am Montag, 21. August 2006 11:43 schrieb Gallai J=E1nos:
> I'm an administrator of a big company who has a PgSQL-database version
> 7.4.2. We would like to upgrade it to 8.1.4 but the dump we made cannot=
be
> restored. We got a lot of error messages while restoring database relat=
ed
> on something's being restored before other objects would exists.
You should have more success if you use the pg_dump(all) program from 8.1=
..4 to=20
create the dump.
--=20
Peter Eisentraut
http://developer.postgresql.org/~petere/
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
Re: Migration from 7.4.2 to 8.1.4
am 09.09.2006 05:11:55 von Michael Fuhr
[Please copy the mailing list on replies so others can contribute
to and learn from the discussion.]
On Fri, Sep 08, 2006 at 12:42:45PM +0200, Gallai J=E1nos wrote:
> Thanks for your help, we tried but the same errors occurs. Would you be=
so
> kind to help us?
> We have tried a lot of things but it seems the only way is to make it b=
y
> hand and it would be a very long work......
Could you show the exact dump and restore commands you ran and a
few of the errors? Are you sure you ran the new (8.1.4) pg_dump
or pg_dumpall against the old (7.4.2) database?
--=20
Michael Fuhr
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster