Forum OpenACS Development: OpenACS 5.8.0 + PostgreSQL 9.3
all the best
I am not sure, why you would expect that the number of failures decreases as the pg version increases. In general, the bugs in OpenACS are not consequences of bugs in pg. I would rather expect the numbers of failures to increase, since new version of pg have properties that were unknown at the time the openacs code was developed.
When you first released 5.8, what version of postgres did you have running? Was it that version of pg which you first run the core tests on?
Did you run those core tests again with 5.8 on any other postgres, and if so which, and were there any differences between those results, and if so do you find them significant? Would you be willing to summarize at least one pair of results you compared?
Concerning bugs etc.: The most important contribution of OpenACS 5.8.0 are that it runs on pg 9.2+ without any necessary configuration changes, and it runs efficiently also on large sites (using e.g. recursive queries for permissions). Before that, large sites had to use pg 8.3, which is already at EOL. Without the change, OpenACS would have been doomed on the longer range.
Concerning pg-versions: we run the regression tests (automated testing on acs-core) on the following pg releases: 8.4.16, 9.0.10, 9.1.5, 9.2.3, 9.2.4, all with the same results (8 errors in spell-check, complains about non-configured spellcheck, an entry about this is active in the bug tracker) and two complaints from acs-authentication (auth_password_recover, auth_password_retrieve; tries to send mail, which is on the test machines not configured). As i wrote earlier, these are exactly the same errors we were seeing with OpenACS 5.6.0 and 5.7.0 ... and now with pg 9.3.0.
The regression test does certainly not cover all of OpenACS. Here are two more figures concerning bug fixing that one might find interesting:
- this year, so far 78 bugs from the bug-tracker were fixed/resolved/closed, this is more than the sum from the previous 4 years (between 5 and 20 per year)
- OpenACS.org runs the freshest code from the oacs-5-8 branch and uses not only acs-core, but as well several packages, in which we fixed many bugs not contained in the bugtracker. These changes led to much lower numbers of error entries in the error.log: 100 days ago (using aolserver + OpenACS 5.5 + pg 8.3.5) we saw abut 17.000 errors per day, last week, we were at 3000, yesterday at 428 (many of the remaining errors are from from invalid urls, etc.). Several bugs were site-related and a single bug could cause many errors/day, but we are feeding all changes back to the oacs-5-8 branch. Eventually this branch will comes out as a OpenACS 5.8.1 release (don't ask me when).
hope, this helps
And yes, you've completely answered my question about whether pg version is influencial over test results; according to your message, it's not influencial as the results are the same for 8.4 and all the 9.x pgs running when you've run the regression tests. Thanks for that too.
the point is this, I intend to customize dotLRN for a virtual classroom at the University of El Alto, Bolivia, I find a lot of material, I have problems with the installation of OpenACS 5.8.0. I hope you can help me with some documentation Thanks
Currently, just the 41 packages on the oacs-5-8 branch  and the packages in used on openacs.org (e.g. edit-this-page, workflow, bugtracker, photo-album) are adapted for PostgreSQL 9.3, for other packages this work is not done. Some packages of DotLRN might work out of the box, some will require work.
In case you want to install a fresh OpenACS 5.8.0 + Postgres 9.3 installation from scratch, check out the scripts  and replace in the configuration part of install-oacs.sh the "HEAD" branch with "oacs-5-8" to obtain the latest from the oacs-5.8.
In case you want to upgrade postgres of an existing installation to 9.3, see , but be aware, that not all packages might work; we are using on production system a modified version of dotlrn mostly with xo*-based packages with PostgreSQL 9.2, so we might be able to help you through the necessary modifications, when you tell us what exact problems you are experiencing.
all the best
As Jim referenced above, many thanks to Gustaf and the faithful few who have kept this project alive.