Re: Upgrading from 7.1 - Mailing list pgsql-general

From Jonathan Villa
Subject Re: Upgrading from 7.1
Date
Msg-id 27679.206.166.29.228.1122497031.squirrel@mail.innovativesource.net
Whole thread Raw
In response to Re: Upgrading from 7.1  (Richard Huxton <dev@archonet.com>)
Responses Re: Upgrading from 7.1
List pgsql-general

My approach will be/has been as follows:

I've used pg_dump of 7.4 to do

pgsql-7.4 $>pg_dump --schema-only dbName > schema.sql

Aside from some tweaking, the import seemed to work fine.

Now, I'm attempting the following

pgsql-7.4 $> pg_dump --data-only --inserts dbName > data.sql

and when I attempt an import, I get

ERROR:  insert or update on table "doc_data" violates foreign key constraint
"docdata_languageid_fk"
DETAIL:  Key (language)=(1) is not present in table "supported_languages".

Regarding the violations of the foreign key contraints, I've been able to
export/import from 7.1 to 7.1 ok.

When I was doing the schema.sql import, I did receive a lot of messages regarding
implicit indexes being created?  Is this something I should be worried about?

Reason I'm not moving to 8.0 is because the application I'm trying to get upgraded
does not give it it's seal of approval.


-Jonathan

<quote who="Richard Huxton">
> Jonathan Villa wrote:
>> I've been googling a little bit and appears that 7.1 pretty old.
>> What steps are advised to upgrade from 7.1 to 7.4?
>
> 1. Dump the old db using 7.4's pg_dump.
> 2. Read the release notes for the in-between versions to make sure
> nothing will impact your behaviour. Keep a close eye for tightening-up
> error checking, or changing typecasting rules etc.
>
> If I was you I'd go straight to 8.0 - it's not going to be noticably
> more work and brings you bang up to date.
>
> --
>    Richard Huxton
>    Archonet Ltd
>



pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: DELETE with JOIN syntax
Next
From: Jaime Casanova
Date:
Subject: Re: Bad plan when null is in an "in" list