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.
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
Good day. I just finished upgrading my AWS RDS database engine from 9.6.22 to 10.17. I used these steps to make the upgrade using the AWS Console:
Create snapshot of target database to upgrade
Restore snapshot
Upgrade the restored snapshot's (which is now a new instance) DB Engine version.
After I did all of this, everything seems fine but when I access the database, this warning message appears
WARNING: psql major version 9.6, server major version 10.
Some psql features might not work.
I did not continue on my testing because I want to know what is the meaning of this first. Because I am fairly new in AWS as a whole. Thanks!
The meaning is that just because you are connecting to an upgraded database on some machine run by Amazon, the PostgreSQL installation on your local machine was not magically updated. psql from version 9.6 doesn't know what metadata tables were changed in v10, what features were removed and so on.
It would be a good idea to install a more recent version of PostgreSQL on your machine. By the way, upgrading to v10 was not the smartest move, as that version will go out of support in less than a year. You should upgrade to the latest version that your service provider offers.
The client program psql you are using to connect to the database is from an older version than the database it is connecting to. Some of the introspection features might not work. For example, psql from 9.6 won't know how to do tab completion for commands that were added to the server after 9.6.
This is generally not a major problem for psql (unless the server wants to use SCRAM authentication), but for optimal experience it would be good to install a newer client. Other tools like pg_dimp might not with at all against a server newer than they are.
Can you upgrade Postresql-server directly from 9.2 to 9.6? (Running on RHEL 7)
yes:
https://www.postgresql.org/docs/9.6/static/pgupgrade.html
pg_upgrade supports upgrades from 8.4.X and later to the current major
release of PostgreSQL, including snapshot and alpha releases.
https://www.postgresql.org/docs/9.6/static/app-pgdump.html
Because pg_dump is used to transfer data to newer versions of
PostgreSQL, the output of pg_dump can be expected to load into
PostgreSQL server versions newer than pg_dump's version. pg_dump can
also dump from PostgreSQL servers older than its own version.
(Currently, servers back to version 7.0 are supported.) However,
pg_dump cannot dump from PostgreSQL servers newer than its own major
version; it will refuse to even try, rather than risk making an
invalid dump.
ephasis mine
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.