Upgrade PostgreSQL from version 16 to 17 in Docker configuration #66
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades the PostgreSQL database version from 16 to 17 in the Docker Compose configuration, as requested in the issue comments where @acbart mentioned they had upgraded to PostgreSQL 17 and needed to update the Docker images accordingly.
Changes Made
docker-compose.ymlto usepostgres:17instead ofpostgres:16-bullseyeCompatibility Analysis
PostgreSQL 17 maintains full backward compatibility with applications using PostgreSQL 16, so no code changes were required:
psycopgandpsycopg2drivers in requirements.txt are fully compatible with PostgreSQL 17CREATE INDEX CONCURRENTLYand PostgreSQL functions likeconcat(),md5(),random()) work correctly with version 17Benefits
PostgreSQL 17 brings performance improvements, enhanced security features, and better resource management while maintaining the same API compatibility that the BlockPy server currently relies on.
Testing
Fixes #62.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.