From: | "Marion McKelvie" <marion(at)streamlet(dot)co(dot)uk> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: restoring large objects |
Date: | 2004-04-07 07:43:50 |
Message-ID: | MPEMKONPODHGLICHEKEGCEJDCOAA.marion@streamlet.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Good idea but I'm not sure if the application will then handle the changed
column type correctly. I'll give it a go and let you know...
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org]On Behalf Of Tom Lane
Sent: 07 April 2004 07:08
To: Marion McKelvie
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] restoring large objects
"Marion McKelvie" <marion(at)streamlet(dot)co(dot)uk> writes:
> Many thanks - you're right, the references are stored (by the application
> using the database) in a column of type text.
Yuck :-(. A possible solution is to dump the schema and data separately
(schema in a plain text dump, data in an -Fc or -Ft dump since plain
text doesn't support dumping LOs). Then manually edit the schema file
to change the column data type to "oid". Then load. I honestly am not
sure that this will work cleanly, but it's worth trying --- and if it
doesn't work, please let me know where it goes wrong.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
From | Date | Subject | |
---|---|---|---|
Next Message | Marion McKelvie | 2004-04-07 09:28:34 | Re: restoring large objects |
Previous Message | Grega Bremec | 2004-04-07 07:18:58 | Re: Raw devices vs. Filesystems |