Fix: PostgreSQL APT repository configuration + repository priority - #396
Open
CelestineSauvage wants to merge 8 commits into
Open
Fix: PostgreSQL APT repository configuration + repository priority#396CelestineSauvage wants to merge 8 commits into
CelestineSauvage wants to merge 8 commits into
Conversation
Removed deprecated lines for PostgreSQL repository setup.
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.
Fix PostgreSQL APT repository configuration
Description
This PR fixes two issues in the PostgreSQL APT repository configuration:
Changes
Replace deprecated
apt-keyusageapt-keywith a dedicated keyring.signed-by.Fix package priority and dependency resolution
Add APT pinning to ensure PostgreSQL-related packages are preferred from the PGDG repository.
Prevent APT from mixing packages from the Ubuntu repository and PGDG when resolving dependencies.
This fixes installation failures such as:
PostgreSQL packages (
postgresql-*,postgresql-client-*,libpq5,libpq-dev) are given a higher priority from PGDG, while other packages from the PGDG repository keep a lower priority.Conclusion
Use the recommended APT key management approach and ensure consistent package selection during dependency resolution, avoiding conflicts caused by packages being selected from different repositories.