Forum OpenACS Q&A: moving to PG 7.2....
As we work on dotLRN, it's become evident that maintaining 7.1
and 7.2 compatibility is kind of a pain at development time. 7.2
has some nice new features (like create or replace) that make
maintenance that much nicer.
We're seriously considering moving the requirements for
dotLRN to PG 7.2, given that a 7.1 to 7.2 migration is mostly
painless. I also want to get people's read on moving OpenACS
4.6 (the next version) to a 7.2 requirement. Thoughts on this?
Traditionally we've supported "Version N and N-1" where "N" is the current version. PG 7.3 is going to start rolling out in at least preliminary form in September making it "N", apparently, so requiring PG 7.2 as a base while also working to make sure we work with whatever new incompatibilities the PG gifts us in PG 7.3 sounds like the right strategy to me.
Trying to make things work with PG 7.1, 7.2 *and* 7.3 sounds unjustifiably complex to me.
We have sites that used to run on Illustra then migrated to Postgres 6... 7.0... then to 7.1. I don't know how much it can still take.
Do you think its safe to run to postmasters in a single box? One in 7.1 and another 7.2?
ERROR: triggered data change violation on relation "acs_objec t_context_index"and related items. I hear this was fixed in postgresql 7.2.
Dave: you're right and that's a very good reason right there to upgrade!