pg_dump and restore problem (7.0.? to 7.2)

From: Paul Warner <pwarner(at)dibinst(dot)mit(dot)edu>
To: pgsql-admin(at)postgresql(dot)org
Cc: dtsai(at)mit(dot)edu, ashrafi(at)mit(dot)edu
Subject: pg_dump and restore problem (7.0.? to 7.2)
Date: 2002-06-19 14:08:19
Message-ID: 3D109053.F8CFEBEB@dibinst.mit.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hello,

I've looked for this in the books and archives and
haven't been able to find an answer.

I did a pg_dump on an older postgres database (I
believe it's 7.0.something), and restored to 7.2.1
with multibyte capability. The old db is not
multibyte. What's happened is that there are a
significant number of rows in the dump file that are
not getting loaded into the new database. The tables
are getting there, but not the data.

I notice that there are triggers added in 7.2 that
don't appear in the earlier version (as in: Triggers:
RI_ConstraintTrigger_1663276). I don't know if this
is related, but it is true that all the 952 messages
related to a certain topic didn't make it into one
table.

This strikes me as a version issue related to
integrity constraints, but could it be related to the
change to multibyte?

I'm working on FreeBSD 4.5, with aolserver and openacs
3.2.4.

Thanks very much for your help!

Paul Warner

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rajesh Kumar Mallah. 2002-06-19 14:36:54 Re: really important
Previous Message Tom Lane 2002-06-19 13:25:31 Re: index keeps on growing