Fix PostgreSQL version to v17 to prevent automatic upgrades to v18 - #87
Merged
snickerjp merged 1 commit intoOct 9, 2025
Merged
Conversation
Member
Author
|
✅ Verification completed I have successfully tested this fix with Redash version 25.8.0: Test Results:
The fix is ready for merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #86
This PR addresses the PostgreSQL 18 directory path issue by fixing the PostgreSQL version to v17 in the Docker Compose configuration.
Changes:
pgautoupgrade/pgautoupgrade:latesttopgautoupgrade/pgautoupgrade:17-to-17The fix ensures that existing Redash installations continue to work without requiring manual intervention for PostgreSQL directory path changes.