Re: [ADMIN] Migration from 7.4.2 to 8.1.4
[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ános 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 by 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? -- Michael Fuhr ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [ADMIN] Migration from 7.4.2 to 8.1.4
Am Montag, 21. August 2006 11:43 schrieb Gallai János: 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. You should have more success if you use the pg_dump(all) program from 8.1.4 to create the dump. -- 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: [ADMIN] Migration from 7.4.2 to 8.1.4
On Mon, Aug 21, 2006 at 11:43:28AM +0200, Gallai János 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). -- 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
