-
Notifications
You must be signed in to change notification settings - Fork 107
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
Feature/upgrade pgbouncer and pgpool #2462
Feature/upgrade pgbouncer and pgpool #2462
Conversation
* Removed auto generated vars * Updated postgresql default configuration with correct settings * Updated tests according to the new version * Increased postgresql, pgaudit, pgpool, repmgr versions * Postgres installation * Repmgr RedHat installation * Commented pgbouncer package not to fail installation * Ubuntu installation except pgbouncer * Updated components * Added molecule tests and documentation * Modified vars * Asciidoc to markdown * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/molecule/debian-repmgr/prepare.yml Co-authored-by: to-bar <[email protected]> * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/molecule/debian-repmgr/verify.yml Co-authored-by: to-bar <[email protected]> * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/molecule/redhat-repmgr/prepare.yml Co-authored-by: to-bar <[email protected]> * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/templates/pg_hba.conf.j2 Co-authored-by: to-bar <[email protected]> * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/tasks/extensions/replication/extension.yml Co-authored-by: to-bar <[email protected]> * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/tasks/extensions/replication/extension.yml Co-authored-by: to-bar <[email protected]> * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/tasks/extensions/replication/extension.yml Co-authored-by: to-bar <[email protected]> * Applied requested changes after review * Update core/src/epicli/data/common/ansible/playbooks/roles/postgresql/tasks/main.yml Co-authored-by: to-bar <[email protected]> * Fixed repmgr check * Require 2 hosts for replication * Improve molecule tests * Add {{ ansible_managed }} to templates * Remove unused templates * Improve task names * Do not hide all failures of "Get cluster status" task Co-authored-by: atsikham <[email protected]> Co-authored-by: to-bar <[email protected]>
…ixed" This reverts commit 5ffa5ba.
…any-platform/epiphany into feature/upgrade-postgresql
This reverts commit acde46b.
… to be fixed"" This reverts commit 8401885.
…ixed" This reverts commit 5ffa5ba.
This reverts commit 962a1c5.
This reverts commit a1ff33d.
This reverts commit d8d7306.
This reverts commit fcd3fe2.
* Get rid of cacheable facts * Applied review suggestion with ternary filter Co-authored-by: atsikham <[email protected]>
Target branch |
… into feature/upgrade-pgbouncer
476dfe7
to
81cb62d
Compare
...picli/data/common/ansible/playbooks/roles/applications/templates/pgpool/04-deployment.yml.j2
Show resolved
Hide resolved
...picli/data/common/ansible/playbooks/roles/applications/templates/pgpool/04-deployment.yml.j2
Show resolved
Hide resolved
...picli/data/common/ansible/playbooks/roles/applications/templates/pgpool/04-deployment.yml.j2
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just for your info:
I see there are already the newest versions:
Pgpool 4.2.4
Bitnami link
PGbouncer
Bitnami link
There is also one fix in md5 context
81cb62d
to
9091ee6
Compare
Thanks, we don't use md5 encryption with plain-text passwords, so i think this should not impact our configuration |
Applies also to task #2076 |
Upgrade pgpool to v4.2.3 and pgbouncer to v1.15
This PR contains also changes from #2428 since those components should be tested in one pipeline
HA with pgpool and pgbouncer works only with md5 passwords - support for scram sha-256 will not be added in this case since it's impossible to automate generate users files basing on SHA.
Postgres
PgPool:
PgBouncer: