Re: [GENERAL] Restoring a Databases that features tserach2 - Mailing list pgsql-admin

From Tom Lane
Subject Re: [GENERAL] Restoring a Databases that features tserach2
Date
Msg-id 25783.1082641667@sss.pgh.pa.us
Whole thread Raw
In response to Re: Restoring a Databases that features tserach2  (Fischer Ulrich <ulrich.fischer@aerodynamics.ch>)
Responses Re: [GENERAL] Restoring a Databases that features tserach2
List pgsql-admin
Fischer Ulrich <ulrich.fischer@aerodynamics.ch> writes:
> pg_dump (PostgreSQL) 7.3.2

>    (pg_dumpall -g GLOBALobjects.sql)
>    pg_dump -s DATABASE > DBschema.sql
>    pg_dump -Fc DATABASE > DBdata.tar

> and rebuilt on the new system with:

> psql (PostgreSQL) 7.4.1
>   1.   createdb DATABASE
>   2.   (psql DATABASE < GLOBALobjects.sql)
>   3.   psql DATABASE < tsearch2.sql
>   3.a. psql DATABASE < setup_ge_ispell.sql
>   4.   psql DATABASE < DBschema.sql
>   5.   pg_restore -N -a -v -d DATABASE DBdata.tar

This is certainly not going to work because the dump from the old
database will already have all the tsearch2 objects, not to mention
whatever setup_ge_ispell.sql may create.  You should get rid of steps
3 and 3a.

> There is no difference when dumped with "pg_dump (PostgreSQL) 7.4.1". I
> get the same error. When I do not update the dict-settings
> (setup_ge_ispell.sql) I can not even restore the other datas.

If you're still having trouble, try dropping the -N option to pg_restore.
I don't know why that option even exists ... there is no practical use
to it AFAIK.

            regards, tom lane

pgsql-admin by date:

Previous
From: "Kevin Schroeder"
Date:
Subject: Transaction log file screwed up
Next
From: Fischer Ulrich
Date:
Subject: Re: [GENERAL] Restoring a Databases that features tserach2