From: | Ron Snyder <snyder(at)roguewave(dot)com> |
---|---|
To: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | trying to upgrade and keep large object IDs intact... |
Date: | 2002-03-04 20:49:13 |
Message-ID: | F888C30C3021D411B9DA00B0D0209BE8026E2D13@cvo-exchange.cvo.roguewave.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
We're trying to move from 7.1.3 to 7.2, and we have a table that stores the
loid from pg_largeobject. The table that references the loid is storing it
as a text field. When we go through the dump/restore process, the loid (for
the attachment, in pg_largeobject) is changed in the new database, which
causes inconsistencies in our data.
We're doing the pg_dump like this:
pg_dump --blobs --format=c --quotes --oids --compress=5 quickview > qv.dump
and the restore like this:
pg_restore -o --dbname=quickview --superuser=pgsql72 < qv.dump
The field (in table "attachments") that references the loid (in
pg_largeobject) is storing the loid as text-- is that possibly what's making
it difficult for us to do this upgrade?
I've read the man pages for pg_dump/pg_restore, as well as searched the web
and the postgres web site, but I'm still lacking the necessary clue to make
this upgrade succeed. Pointers to additional documents happily accepted.
-ron
Table "attachments"
Attribute | Type | Modifier
------------+--------------+----------
id | integer |
atype | character(1) |
data | text |
compressed | boolean |
Index: attachments_id
Rule: att_lo_remover
Trigger: RI_ConstraintTrigger_11991716
From | Date | Subject | |
---|---|---|---|
Next Message | Dino Hoboloney | 2002-03-04 21:23:20 | Re: SQL statement : list table details |
Previous Message | mdb | 2002-03-04 20:48:58 | Temp Tables |