Pg 13

[jburel]

This PR upgrade postgres to version 13. A change in docker-compose is required to start the pg container since password needs to be provided.

The following migration workflow has been tested on new ci:

• Do a DB dump i.e. sudo docker exec -t PG_CONTAINER_ID pg_dumpall -c -U postgres > /tmp/dump_`date +%d-%m-%Y"_"%H_%M_%S`.sql
• Delete pgdata directory
• run docker-compose -f docker-compose up
• Check that Postgres:13 container is up by running docker ps
• Copy the DB dump file to the Postgres:13 container i.e. docker cp dump_12-01-2023_11_47_22.sql PG_13_CONTAINER_ID:/tmp
• Connect to the container's bash terminal docker exec -it PG_13_CONTAINER_ID bash
• Import the DB: psql -U postgres -d postgres < /tmp/dump_xxx.sql
• Check that the OMERO-server and OMERO-test-integration have been created psql -U postgres -l

[sbesson]

Conceptually, the proposed PostgreSQL upgrade makes complete sense and is inline with the support levels published as per ome/omero-documentation#2262.

As noted in the description, probably the biggest challenge is to test the actual upgrade of the DB used for testing. On this front, I'll note there is some internal location where we store a reference snapshot of the training database and binary repository (/uod/idr/repos/outreach). Rather than using a temporary location with all the associated issues, an option might be to start taking and managing snapshots of the testing database/binary repository in a similar fashion. /cc @pwalczysko

[pwalczysko]

Rather than using a temporary location with all the associated issues, an option might be to start taking and managing snapshots of the testing database/binary repository in a similar fashion. /cc @pwalczysko

This makes perfect sense to me.