Re: Problems with pg_restore
От | Tom Lane |
---|---|
Тема | Re: Problems with pg_restore |
Дата | |
Msg-id | 21140.1103563441@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Problems with pg_restore (Kaloyan Iliev Iliev <news1@faith.digsys.bg>) |
Ответы |
Re: Problems with pg_restore
|
Список | 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 по дате отправления: