support Postgres versions 14 and 15

[donsizemore]

What this PR does / why we need it:

add flyway and installer support for Postgres versions 14 and 15

Which issue(s) this PR closes:

• Closes Postgres 15: permissions errors on public schema #9717

Special notes for your reviewer:

None

Suggestions on how to test this:

Install Dataverse using installer and warfile built from branch, run E2E tests.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No

Is there a release notes update needed for this change?:

Perhaps, to explain the support (but not requirement) of the newer Postgres versions.

Additional documentation:

Added: https://dataverse-guide--9877.org.readthedocs.build/en/9877/installation/prerequisites.html#postgresql

[pdurbin]

I didn't test the installer but I tested in Docker. Looks good. Approved. Thanks, Don!

[pdurbin]

This is what I wrote in Slack on Friday:

To summarize, @don and I created https://github.com/gdcc/api-test-runner/actions/workflows/postgres15.yml and containerized Postgres 15 is working fine, (somewhat surprisingly) even without the "GRANT ALL ON SCHEMA public TO "+pgUser+" he added to install.py (our Docker images don’t use the installer).

The version being tested in that container is PostgreSQL 15.4 (Debian 15.4-1.pgdg120+1).

So yeah, I think we should be open to an issue and PR. His change to the installer is specific to PG 15:

if int(pg_major_version) >= 15:
   conn_cmd = "GRANT ALL ON SCHEMA public TO "+pgUser+";"

Thanks or all the legwork, Don!

Also, I looked at the docs at https://guides.dataverse.org/en/5.14/installation/prerequisites.html and we already say, "We recommend installing the latest version that is available for your OS distribution." So this PR is in line with that. All the examples use Postgres 13 and we say, "The application has been tested with PostgreSQL versions up to 13." We can change the examples when we actually are ready to move developers, test infra, and prod to Postgres 13.

[kcondon]

Found an issue when installing on postgres 13:
Installer exits with: Is this correct? [y/n] y
performing database setup
Admin database connectivity succeeds.
PostgreSQL version: 13
Looks like the user already exists. Continuing.
Couldn't grant privileges on schema public to dvnapp

[donsizemore]

Found an issue when installing on postgres 13: Installer exits with: Is this correct? [y/n] y performing database setup Admin database connectivity succeeds. PostgreSQL version: 13 Looks like the user already exists. Continuing. Couldn't grant privileges on schema public to dvnapp

Fixed (sorry).

[pdurbin]

@donsizemore the fact that API tests are passing as of the second run is great: https://jenkins.dataverse.org/job/IQSS-Dataverse-Develop-PR/job/PR-9877/2/testReport/

My understanding is that PG 13 is being used for that test.

What about a test for PG 15? Would you be able to set up a dedicated Jenkins job for that? If we can get that to pass, I'm comfortable merging this.

For the release note, I'm thinking of something along these lines:

"PostgreSQL 13 remains the tested and supported version. However, the installer and Flyway have been upgraded to support PostgreSQL 14 and 15. See PR #9877 for details."

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:9717-postgres-15

ghcr.io/gdcc/configbaker:9717-postgres-15

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[kcondon]

This looks good to me.

[pdurbin]

Looks good to me too.