Skip site navigation (1) Skip section navigation (2)

Re: Problems with pg_restore

From: Kaloyan Iliev Iliev <news1(at)faith(dot)digsys(dot)bg>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Problems with pg_restore
Date: 2004-12-20 15:52:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
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.


Tom Lane wrote:

>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
>			regards, tom lane

In response to


pgsql-general by date

Next:From: Richard HuxtonDate: 2004-12-20 16:03:49
Subject: Re: Problems with pg_restore
Previous:From: Tom LaneDate: 2004-12-20 15:39:12
Subject: Re: Problems with pg_restore

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group