It's well known problem with dump - is't solved in 7.3 ?
btw, did editing of dump file help ?
Oleg
On Fri, 6 Sep 2002, Markus Wollny wrote:
> Hi!
>
> No, I didn't - the DB is quite large, so it's crucial that dump has got
> acceptable speed - which it hasn't got when using --inserts; as I found
> out it seems to be a matter of sequence of the created objects in the
> dump, anyway, so that wouldn't have helped, I think. As far as I can
> see, dump always writes the table-definitions _before_ the
> customs-datatype-definitions. Which is causing trouble, because the
> statements for creating tables that use custom datatypes like txtidx
> thus result in an error but not in a table. So when the COPY-statement
> follows, which should fill the table, it finds nothing to fill - and
> that causes all these errors.
>
> Regards,
>
> Markus
>
> > -----Ursprungliche Nachricht-----
> > Von: Oleg Bartunov [mailto:oleg@sai.msu.su]
> > Gesendet: Donnerstag, 5. September 2002 20:02
> > An: Markus Wollny
> > Cc: Tom Lane; pgsql-general@postgresql.org
> > Betreff: Re: [GENERAL] Problem with restoring dump (may be
> > tsearch-related)
> >
> >
> > Markus, did you try dump with --inserts option ?
> >
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
