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