Forum OpenACS Development: Re: OpenACS 5.9.0 , Postgresql 9.4, and Naviserver 4.99

3: Re: OpenACS 5.9.0 , Postgresql 9.4, and Naviserver 4.99 (response to 2)

Posted by Khy Huang on 03/24/16 01:33 PM

HI Gustaf,

Thanks for the reply. This is a change from the previous way done with Postgresql 8.x where we created one db and have different users and schemas. Our system administrator went to an Enterprise DB training and it was recommended to go with the one DB approach. Out of curiosity, do you know why OpenACS went into multiple DBs direction ? Thanks.

Regards,
Khy

4: Re: OpenACS 5.9.0 , Postgresql 9.4, and Naviserver 4.99 (response to 3)

Posted by Gustaf Neumann on 03/24/16 04:12 PM

The decision about using separate databases was done before i got involved with OpenACS. Probably at that time the support for multiple schemata in oracle/pg was bad/not existing, so using different dbs for different instances was a no-brainer. The biggest advantage of the multiple schema approach is imho referential integrity across instances, which is not needed for OpenACS.

Separate dbs makes it easier to migrate/upgrade/save one instance, the security separation is easier, etc. but altogether the pros/cons are somewhat even (see e.g. [1])

-g

[1] https://www.brentozar.com/archive/2011/06/how-design-multiclient-databases/

5: Re: OpenACS 5.9.0 , Postgresql 9.4, and Naviserver 4.99 (response to 4)

Posted by Khy Huang on 03/24/16 05:05 PM

Thank You.