PostgreSQL 10 is the new main version after 9.6. But if you look at postgresql.org you will find 10.1?
https://www.postgresql.org/about/news/1801/
Is 10.1 a new bugfix release for 10.0?
Can anyone explain that to me?
In version 10, the versioning method was changed. From the linked page:
Beginning with version 10, a major release is indicated by increasing
the first part of the version, e.g. 10 to 11. Before version 10, a
major release was indicated by increasing either the first or second
part of the version number, e.g. 9.5 to 9.6.
Thus 10 is the major version, 10.1 is the first point release of version 10. 10.2 is due out Feb 8th, 2018
Related
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
Understand from: https://www.enterprisedb.com/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/11/EDB_Postgres_Advanced_Server_Guide.1.80.html
that PL/Java is deprecated in Advanced Server 11 and will be unavailable in server versions 12 or later.
May I know:
What is the recommended replacement for PL/Java in PostgreSQL12?
For my existing UDF in PostgreSQL 9.6.x, etc., which is using the PL/Java, how could I move over to PostgreSQL 12?
Thanks in advance.
Edit: Come to think of it, there was an issue reported back in September 2020 (PL/Java issue 260) about failing to build against EDB PostgreSQL 11. It turned out that EDB had made an API-breaking change to upstream PostgreSQL, by changing an API function and leaving behind only a macro with the old name, instead of a (possibly inline-qualified) wrapper that could be addressed.
That ended up requiring an EDB-specific workaround to be shipped in PL/Java, and that fix has been included since PL/Java 1.6.0 and since PL/Java 1.5.6, which both were released in October 2020.
I am sorry that I did not see this question earlier.
I maintain PL/Java, and I have had no notice from EDB concerning why they have deprecated it. Perhaps they are simply no longer providing a binary package prebuilt by them.
I know of PL/Java in use with PostgreSQL 12 and 13. I believe that to build it from source for use with EDB, it should be built with Visual Studio, following these instructions.
If you are able to learn anything more from EDB about the deprecation, or if you have any difficulty building from source, please feel free to open an issue. Thanks!
I have searched the interwebs for PostgreSQL 10.4 (32 & 64) for Linux platforms and Windows platforms but have been unable to locate any binaries to download. All I can find is the 10.5 version (or 9.x). Any ideas on where to look?
Thanks!
As mentioned in Versioning policy,
the rightmost number denotes the minor release, so 10.5 is the most recent release of PostgreSQL 10:
Minor releases are numbered by increasing the last part of the
version number. Beginning with PostgreSQL 10, this is the second part
of the version number, e.g. 10.0 to 10.1; for older versions this is
the third part of the version number, e.g. 9.5.3 to 9.5.4
10.(x-1) is generally made unavailable as soon as 10.x is released, because 10.(x-1) is the same set of programs, but with known bugs not yet fixed: it should not be prefered over a more recent version.
In most cases, the will to install a specific outdated minor release is due to not knowing the version numbering policy.
I want to Upgrade from Kentico 9 to Kentico 11 ans skipping upgrade K9 to K10. Is it possible?
No, you cannot (and should not) do this.
Please note: The upgrade procedures are not cumulative and you may need to use several upgrade procedures if you're using an old version of Kentico.
https://devnet.kentico.com/download/upgrades
While it may seem like this will save you time, the upgrade scripts are designed only to work between major versions (7 > 8, 8 > 9, 9 > 10 etc.). If you try to run the v11 script on a v9 database, you can expect failures in the upgrade process.
Running through each upgrade in order will reduce the risk here and give you the confidence that your site has migrated correctly.
Read the release notes before you start and make note of the breaking changes (there are quite a few)
Kentico 10 Release Notes
Kentico 11 Release Notes
It is strongly recommended not to do that. You must always upgrade one version (major version) in ahead.
Best regards,
Dragoljub
I am seeing 2 versions (9.0.1 vs 8.2.1) of wildfly which were released on the same day. What is the difference between two versions and why there are 2 versions exist in parallel? I couldn't find it over the internet.
Wildfly ships on a very fast development cycle. Each major release 8.x, 9.x, 10.x contains major changes from the previous version. All current major work is being done on the 10.x beta versions.
The minor versions are for bugfixes related to that particular release. Since there are now people in production with both 8.x and 9.x, any critical bugs or security patches go into one of these releases. It is very possible a security issue could exist and be fixed in both 8.x.1 and 9.x.1.
JBoss EAP, which is based on WildFly, deliberately has a slower release schedule. For each major version they release they offer paid support for 4 years, so they change major versions much slower.
There is a good slide of the lifecycle of WildFly/JBoss on page 9 of this slide-deck from the RedHat Summit in June:
http://videos.cdn.redhat.com/summit2015/presentations/12186_red-hat-jboss-enterprise-application-platform-7-roadmap-new-features.pdf
Here is the official announcement for the pair of releases: -
http://wildfly.org/news/2015/07/23/WildFly-901-and-821/