postgresql-latest 17 (new formula) #192392
Draft
+94
−0
Conversation
This file contains 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
github-actions
bot
added
automerge-skip
cho-m
force-pushed
the
postgresql-latest
branch
from
97671f0
to
5aae784
Compare
github-actions
bot
removed
the
automerge-skip
cho-m
commented
Sep 30, 2024
cho-m
force-pushed
the
postgresql-latest
branch
from
5aae784
to
28b94a7
Compare
cho-m
added
the
maintainer feedback
cho-m
force-pushed
the
postgresql-latest
branch
from
28b94a7
to
1f5484c
Compare
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.
Concept idea. Also was originally writing bin symlinks but now trying out a
PG_VERSIONenvironment variable kind of like how Java tools useJAVA_HOME.For rationale, we had some requests to automatically provide binaries on PATH; however, there are problems for users who may not be familiar with the behavior of PostgreSQL data migrations.
This meta formula provides the symlinks for advanced users who are aware of limitations and want to track latest PostgreSQL.
The main issue with prior
postgresqlname (which still exists renaming topostgresql@14) is that we have users that don't want their PostgreSQL to break onbrew upgrade. Sadly the generic name and external sites may result in users runningbrew install postgresql.The hope is that a separate name and the caveats will provide sufficient info this formula is only for specific users. May also expand caveat to add a "Do not open issues ..." message relating to DB migration.