--Thanks for the reply:
--Now, wait a second. The reason why I'm migrating is because of the
OIDs I have that are greater than 2 billion. At the same time, I've looked
at some resources (and was answered by this list) stating that one solution
is to build version 7.2.x and use the pg_dump from it to migrate data.
--Can someone verify that pg_dump from 7.2.x is NOT backwards
compatible? Am I to understand that I can not use pg_dump from
version 7.1.3 because of the OID > 2 billion AND can not use pg_dump
from 7.2.x because of compatibility? That just doesn't sound right.
--Note: I am still able to get maybe 1/3 of the tables and they
ARE making it to the new database ... it's just when the process
gets to the one table (not sure why ... perhaps the OID issue?) and fails.
--Suggestions? Comments?
--Thanks again!
-X
If the database was created with 7.1.x, I believe you have to use pg_dump built for that version of the database. I think you will find that the pg_dump from 7.2.x is not backwards compatible.
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
Howdy:
Running PostgreSQL 7.1.3 and migrating to PostgreSQL 7.2.1.
While trying to use the new (7.2.1) pg_dump / pg_restore to
grab the data from the 7.1.3 database, I run into an error
when I hit a table:
[snip]
/backup/pg_dump -i -Fc -d testdb | /backup/pg_restore -v -h 192.168.0.2 -d testdb
pg_restore: [archiver (db)] could not execute query:
ERROR: Relation "ref_memmonth_spans" does not exist
pg_restore: *** aborted because of error
[/snip]
I am looking at the table on the database (in 7.1.3) and it
seems okay. My question is: what exactly is this
error talking about and why am I not able to dump the
table *by itself* but I can do the others? (Thought about
it being corrupt, but not sure how to prove that).
Thanks!
-X