PG16 & Update testing #569
Merged
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
Collaborator
MrMegaNova
commented
Jan 23, 2024
MrMegaNova
commented
- Support PG16
- Drop PG11 testing
- Increase testing on distros
There were discrepancies between the postgresql.conf templates in the repository and the most current templates. The templates where thus refreshed to make comparisons between versions easier. In summary, the following was changed: - user customisations were reset to package defaults (log handling, port, ...) - backported settings and comments were included (data_sync_retry, krb_server_keyfile, ...) - role customisation were reset to package defaults (includes)
- The postgresql.conf-16.j2 template was compiled from its package template. - Added postgres 16 settings the role defaults. (>= 16) - Annotated deprecated role defaults. (<= 15)
- added missing required version hints for previous posgres versions 11, 12 and 13 - removed incorrect hints on: - postgresql_data_sync_retry: off is default for 10-16 - postgresql_extension_destdir: "" is default for 10-16 - postgresql_gin_fuzzy_search_limit: 0 is default for 10-16 - added comments from templates to some defaults
Due to changes in 8bc5ff2, on Ubuntu 22.04 installations variables from Debian_22.yml are imported instead of Debian.yml. This leads to postgresql_service_name not being set and thus, the playbook was unable to reload the service on configuration changes.
On the 3 January 2024, PostgreSQL has updated their RPM GPG keys: https://yum.postgresql.org/news/pgdg-rpm-repo-gpg-key-update/
On the 3 January 2024, PostgreSQL has updated their RPM GPG keys: https://yum.postgresql.org/news/pgdg-rpm-repo-gpg-key-update/
566 remove postgresql 11 testing
- Support PostgreSQL 16 - Reset config files to pg default - Fix PGDG repo key
Add pg16 testing & Support testing for rockylinux9, debian12 and ubuntu20.04
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.