Beginning with version 2015 SR2 Polarion replaced the integrated H2 database with PostgreSQL in new installations. PostgreSQL has proved superior for performance and scalability. With version 2016, Polarion replaces H2 with PostgreSQL in existing installations also.
You may know that Polarion uses Subversion as its primary data storage, and Lucene as the main query language for user-defined queries. However, Lucene does not perform well for some types of complex queries, such as can sometimes be needed for reports. So Polarion embeds a SQL database that, in essence, mirrors SVN data so that complex queries (an outer join, for example) can use SQL, which performs significantly better than Lucene, which is better suited to user tools like the Visual Query Builder.
Our goal is to migrate existing Polarion installations to PostgreSQL as seamlessly as possible. The update scripts for Polarion 2016 install and configure PostgreSQL to work with your existing installation and disable the existing H2. Before updating your system, we suggest you check the details for your operating system provided in the Configuration.txt file, which you'll find in the root folder of the update distribution.
Because PostgreSQL's syntax is more strictly ANSI-compliant than H2, some existing user-defined queries formulated with H2's syntax may not work after the migration to PostgreSQL. If, after the update, you find any SQL queries not working you can enable Database Compatibility mode via a new system property: com.polarion.platform.sql.h2CompatibilityMode.
When enabled, Polarion attempts to adjust queries formulated with H2 syntax "on the fly" so that they work with PostgreSQL. This should take care of most incompatibilities. More information will be provided in the a new Help topic: Advanced Administration: Database Cmpatibility (H2, PostgreSQL). TIP: If you want to check this before you update to Polarion 2016, check Help on one of the ALM Test Drive server (after it's updated), or download and install an evaluation copy of Polarion.