Thanks Tom... this reports that there were modifications to the tsearch2
functions. But this is how I worked around the restore problem, for
anyone that has similar issues:
1. pg_dump the 8.0.1 database in archive format.
2. Create an empty database on the 8.0.3 server
3. Run the contrib/tsearch2.sql to add tsearch2 to the empty database
4. Run "pg_restore --list" on the archive and pipe to a file (restore.txt)
5. Edit the restore.txt file and remove all reference to the tsearch2
functions/tables/indexes
6. Run "pg_restore --disable-triggers -L restore.txt" on the archive
file and pipe the output to a sql file "restore.sql"
7. Run the resultant sql file using psql to the restore the database.
I also needed to recreate the users and the access permissions to get
fully up to speed.
I think I could also have fixed the tsearch2 functions in the 8.0.1
database directly, and then the restore would have worked, but as I said
before this was a live system so I did not want to fiddle.
There is now an issue with case sensitivity. But I will start that in a
clean thread.
Regards.
Howard Cole
www.selestial.com
Tom Lane wrote:
>Howard Cole <howardnews@selestial.com> writes:
>
>
>>Interestingly, this is the latest tsearch2 function that ships with
>>8.0.3 - note the slightly different syntax to the one below. It looks
>>like the compatibility issue is caused by this.
>>
>>
>
>Read the 8.0.3 release notes ...
>http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-3
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
>
