-
Notifications
You must be signed in to change notification settings - Fork 577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support PostgreSQL 16 #564
Conversation
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
Thanks for your work, can you please reopen this PR to pull on dev branch ? |
I've changed the base branch to development. I hope this has the intended result, I'm more familiar with GitLab ;-). |
Hi thanks for your quick reply |
No problem. It was that time of the year anyway. 🥳 I'll try to fix this, but I might have to extend the scope to include the removal of PG11 to make it work. Would that be okay? I'll be working in the conditional defaults as discussed in #565 (comment). |
Thanks for your proposal, we want to drop testing on postgresql 11 on every distro. |
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.
I've noticed that on my Ubuntu 22.04 a few variables are not set due to I hope it's okay that I included this in this MR, since without it I'm unable to test my changes. |
On the 3 January 2024, PostgreSQL has updated their RPM GPG keys: https://yum.postgresql.org/news/pgdg-rpm-repo-gpg-key-update/
I've pushed bf99ff3 to address this and successfully smoke tested with the test playbook on Rocky Linux 9, Debian 12, Ubuntu 22.04 and CentOS 8. |
Hi @conscribtor , I'm gonna merge #567, then I will review one more time your MR and merge it |
About the conflict, you''ve done right using ⛔ instead of |
I've merged the current development branch into this PR's branch. I think that we should leave only the last EOL PostgreSQL version in the table. The user can then safely infer that all versions older than that are also EOL. I've included your proposed removal of EOL operating systems, since I think that repositories and GPG keys may become unavailable at any moment, which will lead to confusion if it is marked as working in the matrix. I've also removed Debian 10, since it is now under LTS support (comparable to Ubuntu's 18.04 Expanded Security Maintenance that ends in 2028). |
I'd be happy to leave that to you. I'm unexperienced with Molecule tests. |
Good job ! |
@conscribtor, I just wanted to say thanks for helping out on this. |
resolves #565