Currently, the version of the PostgreSQL server internal to the mathesar/mathesar-prod docker image is 15, and the default version of the PostgreSQL server built as part of our testing, development, and production Docker Compose setups is 13. These are out of date.
Proposed solution
We need to
determine the problems for users if we update these.
For example, a user who uses the production Docker image will not be able to update easily to the newest Docker image if we change the PostgreSQL version.
Perhaps we should publish different editions of production Mathesar docker images for different PG versions.
Based on that discussion, update the versions used for building the prod image, and the versions used by default in the docker compose setup.
Additional context
Apparently, PostgreSQL 17 is likely to come out before 0.1.7, so we should consider trying to get that included in our testing matrix and use it by default for image building.
Problem
Currently, the version of the PostgreSQL server internal to the
mathesar/mathesar-proddocker image is 15, and the default version of the PostgreSQL server built as part of our testing, development, and production Docker Compose setups is 13. These are out of date.Proposed solution
We need to
Additional context
Apparently, PostgreSQL 17 is likely to come out before 0.1.7, so we should consider trying to get that included in our testing matrix and use it by default for image building.