Re: Problems with pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kaloyan Iliev Iliev <news1(at)faith(dot)digsys(dot)bg>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problems with pg_restore
Date: 2004-12-20 15:39:12
Message-ID: 19421.1103557152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Kaloyan Iliev Iliev <news1(at)faith(dot)digsys(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kaloyan Iliev Iliev 2004-12-20 15:52:23 Re: Problems with pg_restore
Previous Message Együd Csaba (Freemail) 2004-12-20 15:05:02 Re: PG8 final when