Re: Problems with pg_restore

You are right again.
I don't want to make permanet changes for this one-time problem.

Yes I find a way to

Use pg_restore to make a text dump script, and then edit that, and then
load it into your newer server.

- pg_restore can output to file not only database. I will edit this file.
Thanks.

Kaloyan

Tom Lane wrote:

>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
>
>
>
>