pg_dump and restore from 7.0? to 7.2.1 problem

From: Paul Warner <paulwwarner(at)yahoo(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Cc: Daniel Tsai <dtsai(at)mit(dot)edu>, Babak Ashrafi <ashrafi(at)mit(dot)edu>
Subject: pg_dump and restore from 7.0? to 7.2.1 problem
Date: 2002-06-18 22:08:30
Message-ID: 20020618220830.92109.qmail@web11908.mail.yahoo.com
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

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

Browse pgsql-admin by date

  From Date Subject
Next Message girija nagaraj 2002-06-19 05:28:42 he "pg_encoding_to_char" error
Previous Message Digital Wokan 2002-06-18 21:58:50 Re: Uppercase field names not found