Fischer,
probable scenario:
after step 3. you have tables pg_ts_* and when you restore your database
you tried to insert duplicated data.
I recommend to see remove any entries related to pg_ts_* tables.
Oleg
On Thu, 22 Apr 2004, Fischer Ulrich wrote:
> Some additional infos to my probl
Fischer Ulrich <[EMAIL PROTECTED]> 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
Oleg,
this is exactly what I tryed to. But after cleaning all the new pg_ts_*
tables I wasn't able to restore my datas. My work arround is now to
rename all keys in the pg_ts_* tables (Ex: pg_ts_dict: dict_name: simple
to simple_old). With this modification the pg_restore worked!
Now I only hav
Fischer Ulrich <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> 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.
> Get rid o
Tom Lane wrote:
Fischer Ulrich <[EMAIL PROTECTED]> 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 D
