Index: openacs-4/packages/acs-core-docs/www/files/package-documentation.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/files/package-documentation.xml,v diff -u -r1.3 -r1.3.2.1 --- openacs-4/packages/acs-core-docs/www/files/package-documentation.xml 7 Aug 2017 23:47:54 -0000 1.3 +++ openacs-4/packages/acs-core-docs/www/files/package-documentation.xml 5 Oct 2021 07:01:19 -0000 1.3.2.1 @@ -48,11 +48,11 @@ This package depends on the core OpenACS functionality and on - OpenFTS. It is PostGreSQL-only - it has not been ported to + OpenFTS. It is PostgreSQL-only - it has not been ported to Oracle. - OpenFTS is the third-party PostGreSQL full text search engine. + OpenFTS is the third-party PostgreSQL full text search engine. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml,v diff -u -r1.60.2.9 -r1.60.2.10 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 2 Sep 2021 16:56:01 -0000 1.60.2.9 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 5 Oct 2021 07:01:20 -0000 1.60.2.10 @@ -864,7 +864,7 @@ package with your package. First step is to create the notification types. To do this a script similar - to the one below needs to be loaded into Postgresql. I create this script in a + to the one below needs to be loaded into PostgreSQL. I create this script in a package-name/sql/postgresql/package-name-notifications-init.sql file. I then load this file from my create SQL file. The following code snippet is taken from Weblogger. It creates a lars_blogger_notif notification type (which was created @@ -1189,7 +1189,7 @@ url="http://openacs.org/forums/message-view?message_id=112943">OpenACS implementation has a few differences in the implementation, to make it work for many languages and the - LIKE construct in Postgres. + LIKE construct in PostgreSQL. @@ -1579,7 +1579,7 @@ Connect to a second database It is possible to use the OpenACS Tcl database API with other databases. In this example, the OpenACS site uses a - PostGre database, and accesses another PostGre database called + PostgreSQL database, and accesses another PostgreSQL database called legacy. Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml,v diff -u -r1.33 -r1.33.2.1 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml 4 Jul 2018 10:20:41 -0000 1.33 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml 5 Oct 2021 07:01:20 -0000 1.33.2.1 @@ -142,7 +142,7 @@ If you get errors like: nspostgres.c: In function `Ns_PgTableList': nspostgres.c:679: warning: passing arg 3 of `Tcl_DStringAppend' as signed due to prototype - then PostGreSQL is probably not in the standard location. The location of PostGreSQL is very dependent on which method was used to install it. To correct the problem, replace LSB with the path to the path to your PostGreSQL installation. Often this is /usr/local/pgsql. + then PostgreSQL is probably not in the standard location. The location of PostgreSQL is very dependent on which method was used to install it. To correct the problem, replace LSB with the path to the path to your PostgreSQL installation. Often this is /usr/local/pgsql. You can use the ldd command to verify Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml,v diff -u -r1.35.2.2 -r1.35.2.3 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml 2 Jul 2020 08:39:25 -0000 1.35.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/maintenance.xml 5 Oct 2021 07:01:20 -0000 1.35.2.3 @@ -693,7 +693,7 @@ Isolating and solving database problems. - Without daily internal maintenance, most databases slowly degrade in performance. For PostGreSQL, see . For Oracle, use exec dbms_stats.gather_schema_stats('SCHEMA_NAME') (Andrew Piskorski's Oracle notes). + Without daily internal maintenance, most databases slowly degrade in performance. For PostgreSQL, see . For Oracle, use exec dbms_stats.gather_schema_stats('SCHEMA_NAME') (Andrew Piskorski's Oracle notes). You can track the exact amount of time each database query on a page takes: @@ -775,7 +775,7 @@ Identify a runaway Postgres query. First, logging must be enabled in the database. This imposes a performance penalty and should not be done in normal operation. - Edit the file postgresql.conf - its location depends on the PostGreSQL installation - and change + Edit the file postgresql.conf - its location depends on the PostgreSQL installation - and change #stats_command_string = false to stats_command_string = true Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml,v diff -u -r1.33.2.2 -r1.33.2.3 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml 2 Sep 2021 16:56:02 -0000 1.33.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml 5 Oct 2021 07:01:20 -0000 1.33.2.3 @@ -367,7 +367,7 @@ Vacuuming [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ export EDITOR=emacs;crontab -e - Add these lines to the file. The vacuum command cleans up temporary structures within a PostGreSQL database, and can improve performance. We vacuum gently every hour and completely every day. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day, and every (*) day of month, month, and day of week. Type man 5 crontab for more information. + Add these lines to the file. The vacuum command cleans up temporary structures within a PostgreSQL database, and can improve performance. We vacuum gently every hour and completely every day. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day, and every (*) day of month, month, and day of week. Type man 5 crontab for more information. 0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --analyze $OPENACS_SERVICE_NAME 0 0 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze $OPENACS_SERVICE_NAME @@ -669,7 +669,7 @@ Set up database environment variables for the site - user. Depending on how you installed Oracle or PostGreSQL, these settings may be necessary for working with the + user. Depending on how you installed Oracle or PostgreSQL, these settings may be necessary for working with the database while logged in as the service user. They do not directly affect the service's run-time connection with the database, because those environmental variables are set by the Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml,v diff -u -r1.22.2.1 -r1.22.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml 2 Jul 2020 08:39:25 -0000 1.22.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml 5 Oct 2021 07:01:21 -0000 1.22.2.2 @@ -12,7 +12,7 @@ - If you are installing PostGreSQL instead of Oracle, skip this section. + If you are installing PostgreSQL instead of Oracle, skip this section. OpenACS &version; will install with Oracle 9i but has not been extensively tested so may still have bugs or tuning issues. See Andrew Piskorski's Oracle 9i notes for guidance. Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml,v diff -u -r1.44.2.1 -r1.44.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml 2 Jul 2020 08:39:25 -0000 1.44.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/upgrade.xml 5 Oct 2021 07:01:21 -0000 1.44.2.2 @@ -83,7 +83,7 @@ Linux/Unix The required platform for OpenACS 4.6 is the same as - 4.5, with the exception of OpenFTS. OpenACS 4.6 and later require OpenFTS 0.3.2 for full text search on PostGreSQL. If you have OpenFTS 0.2, you'll need to upgrade. + 4.5, with the exception of OpenFTS. OpenACS 4.6 and later require OpenFTS 0.3.2 for full text search on PostgreSQL. If you have OpenFTS 0.2, you'll need to upgrade. If upgrading from 4.4, you need to manually run acs-kernel/sql/postgres/upgrade-4.4-4.5.sql. See Bug #632 A computer with OpenACS 4.5. @@ -182,8 +182,8 @@ - PostGreSQL - You must use PostGreSQL 7.3.x or newer to upgrade OpenACS beyond 4.6.3. See Upgrade PostGreSQL to 7.3; + PostgreSQL + You must use PostgreSQL 7.3.x or newer to upgrade OpenACS beyond 4.6.3. See Upgrade PostgreSQL to 7.3; @@ -691,9 +691,9 @@ - Upgrading from PostGreSQL 7.2 to 7.3 - An OpenACS database created in PostGreSQL 7.2 will not - work correctly in PostGreSQL 7.3. This is because 7.2 truncates + Upgrading from PostgreSQL 7.2 to 7.3 + 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. @@ -703,7 +703,7 @@ 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/$OPENACS_SERVICE_NAME/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: + 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/$OPENACS_SERVICE_NAME/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 .