From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kaloyan Iliev Iliev <news1(at)faith(dot)digsys(dot)bg> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problems with pg_restore |
Date: | 2004-12-20 17:24:01 |
Message-ID: | 21140.1103563441@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Kaloyan Iliev Iliev <news1(at)faith(dot)digsys(dot)bg> writes:
> But as I say the file with copy commands contains
> ^(at)^@^(at)TABLE DATA^(at)^@^(at)^@^(at)^@^(at)^@^(at)^@^(at)!^@^(at)^@COPY "tracking_base" FROM
> stdin;
> ^(at)^E^@^(at)^@maria^A^A^(at)^@^(at)^@I^,^(at)^@^[^(at)^@^(at)^@0x9b^A^(at)^@^(at)^A^@^(at)^@^(at)^G^@^(at)^@3944825^(at)^U^@^(at)^@epay_requests_archive
> ^@
> things like that. So how can I change this.
Use pg_restore to make a text dump script, and then edit that, and then
load it into your newer server.
> For me it will be easier to change the schema (which is in normal text
> format). To remove the field from the base table and to add it at the
> end of each table that inherits the base table.
[ shrug... ] If you want to make a permanent change to work around this
one-time problem ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2004-12-20 17:36:36 | Re: A "cascade on delete" constraints deletes AFTER the source is gone?? |
Previous Message | Dearman, Rick | 2004-12-20 17:21:02 | Create a cache DB between web portal and internal DB? |