Was there ever a resolution to this?
---------------------------------------------------------------------------
Tom Lane wrote:
> juanmime@ono.com writes:
> > Here is the solution to the problem:
> > First: We have to restore (only) the structure (schema) of the database
> > pg_restore -Ft -v -s db.tar -d database_name -U postgres -S postgres --disable-triggers
> > Second: Restore the datas
> > pg_restore -Ft -v -a db.tar -d database_name -U postgres -S postgres --disable-triggers
>
> [ scratches head... ] Definitely seems that there is a bug in there
> somewhere, if you have to do it that way. I'll take a look later ...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
