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
Related
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
I was using PostgresSQL version 9.6 with JDBC driver 9.4-1206-jdbc42 to connect to Java. I was using the SimpleJDBCCall of Springs to connect to the database.
However, after the upgrade of PostgreSQL to 10.5, we are unable to use the SimpleJDBCCall API. Any light on this issue will be of great help.
You should never use a version of the JDBC driver that is older than the PostgreSQL server release.
The recommendation is to always use the latest driver version. A new driver will know how to talk to an old server, while an old driver might not know how to talk to a new server.
I installed PostgreSQL on my Ubuntu 16.04 using apt install - it installed PostgreSQL 9.5.12. I want to use cmdbuild 2.5. It gives me 9.4.1204 JDBC driver by default in tar.gz install file.
But I have some wrong with install cmdbuild, so I think that driver version is wrong.
The database driver is here: https://jdbc.postgresql.org/download.html
But there is no 9.5, it's 42?
Which driver should I download if I want to connect postgresql 9.5.12?
Like the page you link to says:
If you are using Java 8 or newer, 42.2.2 JDBC 42.
If you are using Java 7, 42.2.2 JDBC 41.
If you are using Java 6, 42.2.2 JDBC 4.
As the page says, it supports PostgreSQL 8.2 or newer.
Seems the MongoDB release is a significant performance upgrade - ay idea when Spring Data MongoDB will support this version?
Strictly speaking, the MongoDB 3.0 server can even be used with the latest 2.13 Java driver and thus the currently released Spring Data MongoDB 1.6.2. For a full compatibility overview of the driver and server versions, see this wiki page.
The recently released first release candidate of Spring Data MongoDB 1.7 ships support for the MongoDB 3.0 Java driver. This is mostly a compatibility release, we don't target special 3.0 features yet (although you should be able to benefit from an upgrade nonetheless).
Find more information about this in the release train wiki, the JIRA ticket as well as the corresponding section of the reference documentation.
The GA release of Spring Data MongoDB 1.7 is scheduled to be part of the Fowler release train GA end of March.
Spring Data Mongo has 1.7RC1 -> http://docs.spring.io/spring-data/data-mongo/docs/1.7.0.RC1/ Hopefully that one will be released soon.
As Java Driver github repo says, they released a 2.13.0 version on January 29th and it is stable -> https://github.com/mongodb/mongo-java-driver/releases/tag/r2.13.0 It includes all the features for mongo 3.0, but you need to go through the compatibility to upgrade to this version.
Also, they are working on v. 3.0.0. for Java Driver, you can find it here -> https://github.com/mongodb/mongo-java-driver/releases/tag/r3.0.0-beta3 (its still in beta though)
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.