Re: Problems with pg_restore - Mailing list pgsql-general

From Tom Lane
Subject Re: Problems with pg_restore
Date
Msg-id 21140.1103563441@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problems with pg_restore  (Kaloyan Iliev Iliev <news1@faith.digsys.bg>)
Responses Re: Problems with pg_restore  (Kaloyan Iliev Iliev <news1@faith.digsys.bg>)
List pgsql-general
Kaloyan Iliev Iliev <news1@faith.digsys.bg> writes:
> But as I say the file with copy commands contains
> ^@^@^@TABLE DATA^@^@^@^@^@^@^@^@^@^@^@!^@^@^@COPY "tracking_base" FROM
> stdin;
> ^@^E^@^@^@maria^A^A^@^@^@^@I^,�^@^@^[^@^@^@^@0x9b^A^@^@^@^A^@^@^@^@^G^@^@^@3944825^@^U^@^@^@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

pgsql-general by date:

Previous
From: Kaloyan Iliev Iliev
Date:
Subject: Re: Problems with pg_restore
Next
From: Michael Fuhr
Date:
Subject: Re: A "cascade on delete" constraints deletes AFTER the source is gone??