Open Source Document Management System | OpenKM

Can anyone comment on the pros and cons of using HSQLDB vs PostgreSQL?

How would the choice of DB impact migration to new versions of OpenKM?

I'm leaning toward PostgreSQL because the DB can be easily backed up, mirrored, and viewed with other tools (i.e. phpPgAdmin). And, if necessary, the version history and notes of each doc can be recovered / exported. What other factors should be considered in choosing HSQLDB vs PostgreSQL?

PostgreSQL is a good DBMS if you're planning to have a lot of records in your database, for normal companies HSQLDB ( default openkm installation ) is enought, we considering until 25.000 docs are good scenario for HSQLDB, we know some users have 100.000 docs in HSQLDB from my point of view HSQLDB is not designed to get good performance with this number of records and we think from OpenKM is visible that the performance decreases. In a scenarios when you decide to have a lot of documents we think Mysql, PostgreSQL, Oracle, etc... are correct decisions. As I said, for major companies is not necessary, and that's the reason why by default OpenKM server installation comes with HSQLDB by default, we thinking direct DBMS administration for OpenKM ( install, etc... ) is not necesarry. HSQLDB has the advantage that is not needed special installation etc... simply uncompress and you get DBMS installed, for major users that's and advantage ( 90% ) the other 10% will need installing other DBMS

Thanks for the quick reply.

Obviously the initial installation/configuration is a bit more complicatated, but what about migration to future versions of OpenKM? Would migration be any different/more-involved with an external DBM?

Migration procedures are defined here http://wiki.openkm.com/index.php/Migration_Guide normally are the same, from version 5.x to 6.x will be some different because it's major change jboss to tomcat and DBMS has a lot of changes.