[FOLIO-1438] Upgrade to PostgreSQL 10 Created: 24/Aug/18 Updated: 07/Jan/20 Resolved: 09/Apr/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Marc Johnson | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | back-end, ci, core, devops, documentation, platform-backlog, sprint45, sprint48, sprint54 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Core: Platform - Sprint 61 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The RAML module builder (and modules based upon it) has been using PostgreSQL 10 for testing since version 18.0.0 released in February 2018. I believe the stated supported version is still 9.6 (I'm not aware of any use of 10 based features). It would appear some behaviour is different. Julian Ladisch proposed on
Based upon a quick scan of the 10.0 release notes, and the absence of mentions of ICU in the 9.6 documentation, it looks like ICU support was added in 10. Which I imagine means this is needed for
Do we want to change our supported version to 10? If we do, what needs to change in our modules and environments? |
| Comments |
| Comment by Heikki Levanto [ 24/Aug/18 ] |
|
I am using Debian/stable (stretch) on my workstation, and it still has postgres 9.6. On my home machine, I use Debian/testing (buster), and it has version 10 (actually, Debian version 10+192, what ever that means). If we mandate using 10.0 for development, some people may need to install postgres manually, to get to version 10. Not impossible, but a bit of a hazzle, possibly for many people. |
| Comment by Julian Ladisch [ 24/Aug/18 ] |
|
They can use Docker to run Postgres 10.x: docker run --name postgres5433 -e POSTGRES_PASSWORD=postgres -p 5433:5432 -d postgres:10-alpine |
| Comment by Julian Ladisch [ 24/Aug/18 ] |
|
For the major linux distributions there is no need to install postgres 10 manually because repositories for automatic installation are available:
|
| Comment by Hongwei Ji [ 28/Aug/18 ] |
|
Just a FYI: AWS Aurora does not support 10 yet. As of this writing, the latest is PostgreSQL 9.6.9. |
| Comment by Marc Johnson [ 29/Aug/18 ] |
|
Hongwei Ji Is AWS Aurora planned for / is used for some of the FOLIO environments? And if so, does that mean that upgrading to 10 is blocked on this support (or we may need to support both)? |
| Comment by Hongwei Ji [ 29/Aug/18 ] |
|
Hi Marc Johnson yes, we use Aurora in our FOLIO environment. The hope is that AWS will support Aurora PostgreSQL 10 soon. If not, we can fall back to use AWS RDS. I commented it yesterday just a FYI. I was a little surprised to learn that FOLIO needs the latest feature from PostgreSQL to implement some functionalities. |
| Comment by Marc Johnson [ 29/Aug/18 ] |
|
Hongwei Ji I believe a primary driver behind this upgrade is ICU collation support so that we can have localized searching and sorting. If there is an alternative mechanism for that, it might be worth exploring that. At the moment, I believe PostgreSQL use OS provided libraries to perform this, and so can be different depending upon where it is deployed. |
| Comment by Julian Ladisch [ 29/Aug/18 ] |
|
https://aws.amazon.com/rds/aurora/ says: "The Amazon Aurora database engine is fully compatible with existing MySQL and PostgreSQL open source databases, and adds compatibility for new releases regularly." |
| Comment by Julian Ladisch [ 01/Oct/18 ] |
|
Aurora is no longer a blocker of this issue: "Amazon Aurora with PostgreSQL Compatibility now supports PostgreSQL major version 10.4, and is available in US East (N. Virginia, Ohio), US West (Oregon), and Europe (Ireland) Regions." |
| Comment by Julian Ladisch [ 07/Jan/19 ] |
|
"Amazon Aurora with PostgreSQL Compatibility now supports PostgreSQL major version 10.5" |
| Comment by Jakub Skoczen [ 04/Mar/19 ] |
|
John Malconian Wayne Schneider should we consider Postgres 11? |
| Comment by Julian Ladisch [ 04/Mar/19 ] |
|
The supported platforms for postgresql-embedded for postgresql 11 are Mac OS X and Windows x86-64. |
| Comment by Julian Ladisch [ 18/Mar/19 ] |
|
"Amazon Aurora with PostgreSQL Compatibility Supports PostgreSQL 10.6" https://aws.amazon.com/about-aws/whats-new/2019/02/amazon-aurora-with-postgresql-compatibility-supports-postgresql-10-6/ |
| Comment by Cate Boerema (Inactive) [ 09/Apr/19 ] |
|
Hi Jakub Skoczen. It looks like this Core Platform issue is blocking a couple of bug fixes now. Is this on your radar to fix? |
| Comment by Ann-Marie Breaux (Inactive) [ 09/Apr/19 ] |
|
Jakub Skoczen Cate Boerema And once this is fixed, it looks like there might also need to be a change to RMB before the bugs are fixed? |
| Comment by John Malconian [ 09/Apr/19 ] |
|
I'm going to upgrade and test postgresql v10 in our snapshot/testing reference environments today. |
| Comment by John Malconian [ 09/Apr/19 ] |
|
reference environments have been upgraded to postgresql10. Will take effect on tonight's build of folio-testing and folio-snapshot. |
| Comment by Julian Ladisch [ 09/Apr/19 ] |
|
Ann-Marie Breaux: To fix the sorting bugs the default sorting (=collation) of the databases need to be changed.
The changes needed for RMB (
|
| Comment by Ann-Marie Breaux (Inactive) [ 09/Apr/19 ] |
|
Julian Ladisch Thank you so much for jumping on this, and for
|
| Comment by Jakub Skoczen [ 10/Apr/19 ] |
|
John Malconian Julian Ladisch the issue we discussed during the stand-up was
|