Forum OpenACS Q&A: Recommended version of PostGreSQL for 4.6.2?

Collapse
1: Recommended version of PostGreSQL for 4.6.2?
Posted by Joel Aufrecht on 04/17/03 08:27 PM
What should I put in the docs for the Reference Platform for OpenACS 4.6.2?  I'm inclined to be conservative and stick with 7.2.3, because the priorities for the Reference platform are 1) Stable 2) Reliable 3) Secure 4) Functional, in that order.  Similarly, I'll stick with Red Hat 8.0 (plus a patch for that kernel security hole, I think) unless someone has strong arguments for a different package.
Collapse
2: Re: Recommended version of PostGreSQL for 4.6.2? (response to 1)
Posted by Don Baccus on 04/18/03 12:07 AM
PG 7.2.3 is the safe choice.  While I did the work necessary to support PG 7.3.x for 4.6.2 I don't know of anyone who's tested it thoroughly in a production environment.  And 7.3.0 had a bug in it that kept OpenACS from installing (7.3.1 and newer versions work fine.)

So all in all I'm fine with sticking with 7.2.3 for the reference platform while encouraging all of our developers and keyed-in avant garde users to use 7.3.x if at all possible (all my development the last four or so weeks have been on 7.3.x so indeed it does seem to work fine.)

Collapse
3: Re: Recommended version of PostGreSQL for 4.6.2? (response to 1)
Posted by Lamar Owen on 04/18/03 08:41 PM
PostgreSQL 7.2.x is currently at 7.2.4, not 7.2.3.

Here's the announcement from the PostgreSQL web site.
PostgreSQL 7.2.4 released
Posted on 2003-01-31
Posted by justin@postgresql.org

In order to address several critical issues that have been recently identified, we have tag'd and packaged up a v7.2.4 release of PostgreSQL, aimed at those unable to upgrade to the v7.3 code.

Major changes in this release are:

  • Fix some additional cases of VACUUM "No one parent tuple was found" error

  • Prevent VACUUM from being called inside a function (Bruce)

  • Ensure pg_clog updates are sync'd to disk before marking checkpoint complete

  • Avoid integer overflow during large hash joins

  • Make GROUP commands work when pg_group.grolist is large enough to be toasted

  • Fix errors in datetime tables; some timezone names weren't being recognized

  • Fix integer overflows in circle_poly(), path_encode(), path_add() (Neil)

  • Repair long-standing logic errors in lseg_eq(), lseg_ne(), lseg_center()


This release is backwards compability to the previous v7.2.x releases, and does not require a dump/restore to upgrade.

Due to the extent of the changes between v7.2.x and v7.3.x, as pertains to the use of bison, for those wishing to build from CVS, you will need the older version of bison. bison v1.75+ will not work.

This release can be found on all mirrors, as well as the main site, under:

/pub/source/v7.2.4
Collapse
4: Re: Recommended version of PostGreSQL for 4.6.2? (response to 1)
Posted by Lamar Owen on 04/18/03 09:01 PM
I'll second the recommendation for Red Hat 8, though, at least until NPTL under RHL9 shows itself well with AOLserver.  It may make a significant difference in speed -- but it may also make a big difference in stability.