[FOLIO-2410] EOL: PostgreSQL 9.x Created: 20/Dec/19  Updated: 03/Jun/20  Resolved: 08/Jan/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Johannes Drexl Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: postgres
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Duplicate
duplicates FOLIO-1438 Upgrade to PostgreSQL 10 Closed
is duplicated by FOLIO-2406 SSL/TLS, SCRAM-SHA-256, migration to ... Closed
Sprint:

 Description   

Migration to PG10+ will be mandatory in September 2021, because that's when support for 9.x will be dropped after 5 years of maintenance. Pushing that to the back of the queue will be stressful for the community afterwards, when the deadline draws near, especially with more and more modules being build on legacy functions and more libraries using folio in their production environment.



 Comments   
Comment by Johannes Drexl [ 20/Dec/19 ]

This is a branch of https://folio-org.atlassian.net/browse/FOLIO-2406

Comment by Julian Ladisch [ 07/Jan/20 ]

Johannes Drexl Can you give a more detailed report where FOLIO still uses PostgreSQL 9.x? Please post URLs to the affected documentation/script/installation.

RAML Module Builder (RMB) has switched from 9.6 to 10 in April 2018:
https://github.com/folio-org/raml-module-builder/commit/ac59e211b0323992092bcb6ef177c7c46aacf79b#diff-04c6e90faac2675aa89e2176d2eec7d8R986

The reference environments ( https://dev.folio.org/guides/automation/#reference-environments ) have switched from 9.6 to 10 in April 2019: https://github.com/folio-org/folio-ansible/commit/d2445aaa87fe03aee36a3e63cbd18d53577ee02c

The single server installation documentation has switched from 9.6 to 10 in Juni 2019: https://github.com/folio-org/folio-install/commit/665f5395e21b65f626f24fc55ca873e4586ec748

Comment by Johannes Drexl [ 07/Jan/20 ]

As I'm a SysOp and not a Dev, I look at Folio as a black box system and just try stuff with it. Since Okapi (2.36.0) was not able to work with SSL and SCRAM-SHA-256, the latter of which was introduced with PG 10, it has to either work on a prior version or was stripped to the bones by devs (which would be asking for cattle prod sessions all the way).

So yes, I'm technically able to try to force all modules to talk to my Debian 10 PostgreSQL server via SSL using SCRAM-SHA-256 passwords, but I'm only able to provide hints (i. e. works or not). For me things just have to work in a bullet proof way, that is safe to use and secure in depth.

Comment by Julian Ladisch [ 08/Jan/20 ]

The FOLIO project does not use PostgreSQL 9.x any longer. It has already upgraded to PostgreSQL 10.

I cannot find any usage of PostgreSQL 9.x, therefore I close this issues as "cannot reproduce".

The bug reports about SSL/TLS and SCRAM-SHA-256 are not caused by PostgreSQL 9.x. They already got dedicated issues: FOLIO-2411 Blocked , FOLIO-2412 Blocked , OKAPI-787 Closed

Generated at Thu Feb 08 23:20:26 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.