I am not sure how to be more specific. Basically when I try to restore
a database that has been dumped in which the primary key to a table
has had its name changed the restore fails because it thinks a relation
is missing.
>
> On Fri, Jul 30, 2004 at 11:20:31AM -0500, Jason Tesser wrote:
> > Does anyone know what is going on with my 2nd question below?
>
> I think you'd have to show a specific example.
>
> > > 2. I thought the best way was to create a script that would use
> pg_dump to
> > > create a dump every night and then use restore if I need to. I did
> this
> > > but I am having a problem. Apparently there were a few Primary key
> Big
> > > Serial fields that had the name changed on them after they were
> created.
> > > The backup works fine but during the restore it fails because it
> thinks a
> > > relation is missing. Before restoring the database with the changed
> fields
> > > works fine, I just cannot get it to restore. Is there something in
> the
> > > background that Postgres is hanging on to after I renamed the fields
> that
> > > is preventing me from restoring? How can I work around this?
>
> --
> Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
> "Linux transformó mi computadora, de una `máquina para hacer cosas',
> en un aparato realmente entretenido, sobre el cual cada día aprendo
> algo nuevo" (Jaime Salinas)
