Re: DB Import Error...

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-admin(at)postgresql(dot)org>,<gnanam(at)zoniac(dot)com>
Cc: <raghuchennuru(at)gmail(dot)com>
Subject: Re: DB Import Error...
Date: 2011-04-04 16:12:08
Message-ID: 4D99A788020000250003C21A@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Gnanakumar" <gnanam(at)zoniac(dot)com> wrote:

>> The recommended upgrade technique is to us pg_dump (or
>> pg_dumpall) from the newer version (9.0.3 in this case) to access
>> the old database (running the 8.2.3 server in this case). If you
>> followed some other procedure, like using the 8.2.3 software to
>> dump the database, you should try the recommended approach
>> instead.

> Before trying out to use pg_dump from the newer version (9.0.3 in
> this case), I analyzed (.sql dump file) to my knowledge on what's
> going wrong.

> What I could infer from this based on my knowledge is that the FK
> constraints are dropped from the table but its associated
> constraint triggers are not dropped properly.
>
> How do I resolve/clean-up our database at this stage?

If you're upgrading to 9.0, I would start by following the
recommended upgrade procedure and seeing whether these problems then
exist in the new database. Fixing old issues like this is one big
reason for using the newer version of pg_dump.

-Kevin

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Glyn Astill 2011-04-04 16:23:40 Re: Bloated indexes from pg_restore? (Was: Index fillfactor changed in pg9?)
Previous Message Tom Lane 2011-04-04 16:02:13 Re: Bloated indexes from pg_restore? (Was: Index fillfactor changed in pg9?)