As of this bug report, the Evergreen community only supports Evergreen with PostgreSQL versions 9.6 and 10. According to the PostgreSQL Versioning Policy (https://www.postgresql.org/support/versioning/), the PostgreSQL community will expire support for these versions in November 2021 and November 2022, respectively. While the various Linux distributions may continue to supply security patches on these versions well past those dates, we should not rely on that. Furthermore, the recent tendency has been to install PostgreSQL packages using the PostgreSQL community apt repository (https://wiki.postgresql.org/wiki/Apt) where available.
Since the Evergreen-supported versions of PostgreSQL are soon to be out of support, and since PostgreSQL versions 11, 12, and 13 have all been available for some time, it would behoove us to begin investigating a move to these newer PostgreSQL releases. To that end, Jason Stephenson of CW MARS has started a project to test the Evergreen database on PostgreSQL versions 10 through 13 (and possibly more recent versions as they are ready). The results of this testing will be posted to files in the shared Google Drive folder listed below:
https://drive.google.com/drive/folders/1sRZ8P1RHCOcZx42DxUehvOpoNkJJnfqn?usp=sharing
The following pgtap tests fail when run on PostgreSQL version 12 through 14:
t/authority- update- bib-propagation .pg (Wstat: 0 Tests: 9 Failed: 4) unaccent_ and_squash. pg (Wstat: 0 Tests: 18 Failed: 2) test_preserving _bookbag_ entries. pg (Wstat: 0 Tests: 2 Failed: 1) lp1379815_ vl_import_ item_stat_ cats.pg (Wstat: 0 Tests: 1 Failed: 1) 0824.item_ import_ defaults. pg (Wstat: 0 Tests: 1 Failed: 1) 0847.auth_ overlay_ generator. pg (Wstat: 0 Tests: 1 Failed: 1) lp1145213_ test_func_ asset.merge_ record_ assets. pg (Wstat: 0 Tests: 5 Failed: 1)
Failed tests: 1-3, 7
t/lp1501781-
Failed tests: 7, 12
t/lp1731960_
Failed test: 1
t/regress/
Failed test: 1
live_t/
Failed test: 1
live_t/
Failed test: 1
live_t/
Failed test: 1
A subset of the above tests fail on PostgreSQL 11, but the above list includes all of the tests that also fail on Pg 11.
Fixing the Evergreen code so that these tests succeed on PostgreSQL versions 11 through 14 and continue to work on PostgreSQL 10 would be the logical next step in getting Evergreen working on more recent PostgreSQL version.