OPTIONAL: Install the new OpenFTS Engine.�If you want to upgrade the OpenFTS Engine, do these steps. (You must have already upgraded the OpenFTS driver to - 0.3.2.)
Browse to http://yourserver/admin/site-map
On the openfts line, click on set parameters.
Change the value of openfts_tcl_src_path from /usr/local/src/Search-OpenFTS-tcl-0.2/ to /usr/local/src/Search-OpenFTS-tcl-0.3.2/
Click
[root root]# restart-aolserver service0Browse to http://yourserver/openfts
Click Administration.
Click
An OpenACS database created in PostGreSQL 7.2 will not work correctly in PostGreSQL 7.3. This is because 7.2 truncates function names to 31 characters, but 7.3 does not. This does not cause problems in 7.2, because truncation occurs both at function creation and at function calling, so they still match. But if you use a database created in 7.2 in 7.3, the function names in the database remain truncated but the function calls are not, and so they don't match. Also some functions use casting commands that no longer work in 7.3 and these functions must be recreated.
+ 0.3.2.)
Browse to http://yourserver/admin/site-map
On the openfts line, click on set parameters.
Change the value of openfts_tcl_src_path from /usr/local/src/Search-OpenFTS-tcl-0.2/ to /usr/local/src/Search-OpenFTS-tcl-0.3.2/
Click
[root root]# restart-aolserver service0Browse to http://yourserver/openfts
Click Administration.
Click
An OpenACS database created in PostGreSQL 7.2 will not + work correctly in PostGreSQL 7.3. This is because 7.2 truncates + function names to 31 characters, but 7.3 does not. This does + not cause problems in 7.2, because truncation occurs both at + function creation and at function calling, so they still match. + But if you use a database created in 7.2 in 7.3, the function + names in the database remain truncated but the function calls + are not, and so they don't match. Also some functions use + casting commands that no longer work in 7.3 and these functions + must be recreated.
To upgrade an OpenACS site from PostGreSQL 7.2 to 7.3, first upgrade the kernel to 4.6.3. Then, dump the database, run the upgrade script /var/lib/aolserver/service0/bin/pg_7.2to7.3_upgrade_helper.pl on the dump file, and reply the dump. See Forum OpenACS Q&A: PG 7.2->7.3 upgrade gotcha?. Example:
Back up the database as per PostgreSQL.
Run the upgrade script on the backup file.
[root root]# su - service0 [service0 service0]# cd /var/lib/aolserver/service0/bin [service0 bin]$ ./pg_7.2to7.3_upgrade_helper.pl \ @@ -48,6 +57,20 @@ (many lines omitted) [service0 bin]$
Use perl to replace timestamp with timestamptz in the dump file.
find . -type f -name "*sql" | xargs perl -p -i.tmp -e "s/timestamp with time zone/timestamptz/g" - find . -type f -name "*sql" | xargs perl -p -i.tmp -e "s/\\wtimestamp[^t]/ timestamptz/g"
Install PostgreSQL 7.3.x. Note that you PostgreSQL + find . -type f -name "*sql" | xargs perl -p -i.tmp -e "s/\\wtimestamp[^t]/ timestamptz/g"
Create a new user for PostgreSQL 7.3.x, as per the + Postgres installation guide. Keep in mind that your + installation location is different, and your startup script + (/etc/init.d/postgres73 should be named differently. You + might even need to edit that file to make the paths correct) +
Install PostgreSQL 7.3.x. Note that you PostgreSQL must listen on a different port in order to work - correctly.
Restore the database from dump as per the recovery instructions.