Is there a postgres and keycloak version compatibility matrix? What is the latest postgres version compatible with Keycloak 20 ?
Unfortunately, there's no any matrix. In docs just a short and outdated list and some comments in Github discussions on why it's outdated.
Meanwhile, DB version for Java apps always depends on JDBC driver version.
So, the easiest way to find out what version of PostgreSQL is suitable for KC release is to take a look at versions of JDBC driver and PostgreSQL that specified in pom.xml. Switch to a release tag in the official repository, e.g. https://github.com/keycloak/keycloak/blob/20.0.3/pom.xml#L149-L150
The documentation here suggests Version 10.
The developer commits and issues only mention postgresql without versions. It doesn't matter which version you use, as long as it's supported!
See here for supported versions:
Supported versions
Related
Other than looking over release notes, is there any way to find what versions of postgresql a given version of Flyway would support?
We are trying to upgrade some Postgresql 9.6 servers, so looking for the highest version of Flyway that would support Postgresql 9.6 so we can support both the existing 9.6 and a newer version of Postgresql.
It would be nice if there was a compatibility matrix of Flyway version against database version for each supported database in the docs but if such a thing exists, I haven't found it.
Instead, I've had to resort to a bit of git blame detective work.
For PostgreSQL, the minimum version is checked in PostgreSQLDatabase.java.
Viewing the Git Blame for that file, shows that the minimum community edition-supported version of PostgreSQL was changed to 10 in this commit, which first appeared in Flyway 8.0.0-beta1.
The previous minimum version was 9.5, which would work with your current database version of 9.6, and this can be found in Flyway 7.15.0, which is the latest release before 8.0.0-beta1.
I am running Keycloak server 3.4.3.Final version, that it used JDBC_POSTGRES_VERSION=42.1.4. I want to know which latest Postgres version (10,11,12,13) will compatibility with 42.1.4 driver.
Thanks a lot!
With the JDBC driver 42.1.4 being released on the 1st of August 2017 (2017-08-01) according to the changelog, you can take a look at the state of the release/download page of Postgres at that time using e.g. the Internet Archive.
A page snapshot from November 2017 (some month after the release) reads the following:
Current Version 42.1.4
This is the current version of the driver. Unless you have unusual
requirements (running old applications or JVMs), this is the driver
you should be using. It supports PostgreSQL 8.2 or newer and requires
Java 6 or newer. It contains support for SSL and the javax.sql
package.
If you are using Java 8 or newer then you should use the JDBC 4.2 version.
If you are using Java 7 then you should use the JDBC 4.1 version.
If you are using Java 6 then you should use the JDBC 4.0 version.
If you are using a Java version older than 6 then you will need to use a JDBC3 version of the driver, which will by necessity not be
current, found in Other Versions.
TL;DR: You can use this driver starting with PostgreSQL 8.2.
PostgreSQL release history:
https://www.postgresql.org/docs/release/
https://www.postgresql.org/support/versioning/
PostgreSQL JDBC release history:
https://jdbc.postgresql.org/documentation/changelog.html
I used pkg list entire command , and i got the output for version column as follows :
0.5.11-0.175.1.0.0.24.2.
How to find the SRU from this?
Can we upgrade/ downgrade to a particular SRU ?
SRU is an abbreviation for Support Repository Update, installing new package versions from the support repo for that OS, much like installing a patch cluster for older Solaris releases.
The various fields in the version is explained in Oracle Solaris Package Versioning.
Oracle only makes SRUs available to customers with support contracts - if you have a support contract you can read more about SRU's in the Oracle Support Knowledgebase at Solaris 11 Support Repositories Explained, and see what fixes are available in each SRU for Solaris 11.1 and Solaris 11.2.
If you run 'pkg info entire' it will show the SRU name in human readable format also (if you have installed from the support repo - otherwise it shows the Release info). The 4th digit in 0.175.1.0.0.24.2 is the SRU number
In the example above it is the base Solaris 11.1 release - no SRU has been installed yet.
If an SRU had been installed on top of that you'd get a version like 0.5.11-0.175.1.21.4.1 (aka Oracle Solaris 11.1 SRU21.4.1)
You can easily upgrade to an SRU but you can't downgrade unless you have an older Boot Environment (BE) from which to upgrade to the SRU you want.
Is there a list anywhere or best practice instructions for update firebird databases from one version to another (in my case 2.1.3 to 2.5.2)?
I have seen backup and restore mentioned. I have updated from 1.5 to 2.1 in the past but that just worked i.e. I just installed the new firebird version, however I aware that this was probably just luck.
Regards
The Firebird 2.5.2 release notes has a section on compatibility issues that you need to be aware of when upgrading. Also the Firebird install directory contains additional info on upgrading in misc/upgrade/metadata/metadata_charset.txt. If your database has the incorrect metadata charset things might break (but AFAIK they would have been broken under Firebird 2.1 as well).
Technically you can upgrade to 2.5 without a backup and restore cycle on your database, but that means the On Disk Structure (ODS) of the database isn't upgraded to ODS 11.2, which could mean that you can't actually use some of the new features (or: performance improvements) introduced with the newer version. This could be worse if you are actually still on ODS 10.1 from Firebird 1.5.
I'm trying to install phpPgAdmin as an XAMPP addon when I encountered an error because the latest phpPgAdmin supports upto PostgreSQL version 8.3.x. So I decided to install PostgreSQL 8.3.11 instead of the latest (PGSQL 8.4.x). Will this matter to my OSM application? Thanks!
There are a lot of advantages to Postgres 8.4 over 8.3, and Open Street Map / PostGIS should work on it, so I'd recommend using 8.4 for the Postgres version, and instead grabbing the latest version of phpPgAdmin from the projects github repo (http://github.com/xzilla/phppgadmin), which fully supports 8.4. That will tide you over until the next official phpPgAdmin release, which is scheduled to happen in the next few weeks.
The only link between OSM and postgresql is probably postgis.
Postgis lastest version (1.5.1) requires postgresql >= 8.3, so the answer is no, it won't matter - if, of course, I understood your question correctly.