Re: Problems with pg_restore
| От | Tom Lane |
|---|---|
| Тема | Re: Problems with pg_restore |
| Дата | |
| Msg-id | 19421.1103557152@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | 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:
> [ details omitted ]
The easiest way around this is to use a recent (7.4 or 8.0) pg_dump to
dump from the 7.2 database. That will produce a dump using copy-with-
column-list commands which will be proof against the schema
rearrangement that you seem to have done. (I am guessing that the
"deleted" column was added to the parent table after the fact.)
If you no longer have the 7.2 server active, then you'll have to
hand-edit the dump script to add a column list in the proper order (ie,
the order matching the COPY data) to the COPY command for the child
table.
regards, tom lane
В списке pgsql-general по дате отправления: