Database support for PostgreSQL 9.2 (RHEL/CentOS)

I notice SonarQube 7.3 has now removed support for PostgreSQL 9.2. Why is this? The issue notes for this don’t seem to indicate why this has been done.

MariaDB 5.5/PostgreSQL 9.2 are still the main versions deployed on RHEL/CentOS systems, it would be helpful at least if support for one of these two continued, at least until the next LTS milestone.

Hi,

PostgreSQL 9.2 has been EOL for nearly a year: https://www.postgresql.org/support/versioning/.

Ann

EOL does not mean that it is not still in use.
It is still the main version supported by RHEL/CentOS.

Hi,

It’s not because we don’t mark anymore a db version as not supported that it will not work on SonarQube.
It mainly means that we won’t check anymore that it’s working correctly (we won’t run our internal tests on it).

IMO, it should still work for you.

Regards

That isn’t what your notes state:

PostgreSQL < 9.3 No Longer Supported

SonarQube 7.3+ only supports PostgreSQL 9.3 to 10. SonarQube will not start if you are using a lower version of PostgreSQL.

Yesterday I did an upgrade from 7.1 to 7.3 and I saw an error in the console:

Unsupported PostgreSQL version: 9.2. Minimal supported version is 9.3

SonarQube verifies the database in DatabaseChecker.

From my point of view Centos has a bug, that still the main supported version is 9.2. I did this and it works excellent:

Now I have the latest 9.6.X version.


btw. this topic should be moved to Get Help.

1 Like

Oh yes, sorry I forget that.

So indeed it’s not possible to use PostgreSQL 9.2, I forget that this one is really too old.
You need at least to upgrade to 9.3, even if I you recommend you to jump to 10.X

Regards

Hi Julien,

Thanks for responding, but I would really like to see this enforced limit ‘removed’ unless their a significant technical limit as to why Sonar cannot run on PostgreSQL 9.2 (or MySQL 5.5 for that matter.) If anything I would be curious to know what Sonar is doing that 9.2/5.5 cannot do. If it’s purely as the Sonar team are not testing, then a warning of untested/unsupported would be fine and a risk for us to take.

It’s easy to say ‘just upgrade’, however, in reality that is not always an option.