Thanks Tom,
You are right. I coleage of mine has added the delete column after the
schema was created and it ptobably was on the bottom of the table and
dumped there. But now when I restore the schema this column is on the
top and the copy command wouldn't work. So I must change the schema file
on hand. To remove the column from the tracking_base table, and to add
it manuly on the bottem of each table that inherits it. This should
work. Thanks again.
Kaloyan
Tom Lane wrote:
>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
>
>
>
>
