feat: leverage pgbouncer's auth_dbname#4939
feat: leverage pgbouncer's auth_dbname#4939phisco wants to merge 1 commit intocloudnative-pg:mainfrom
Conversation
phisco
changed the title
|
❗ By default, the pull request is configured to backport to all release branches.
|
cnpg-bot
added
backport-requested ◀️
phisco
changed the title
phisco
force-pushed
the
dev/1383
branch
2 times, most recently
from
aa6fe60 to
73001fa
Compare
|
/test limit=local |
|
@phisco, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/9756580441 |
Signed-off-by: Philippe Scorsolini <[email protected]>
Previously, CloudNativePG configured authentication by creating a `user_search` function in every accessible database and granting CONNECT privileges to the PgBouncer auth_user. This patch simplifies the process by using the `auth_dbname` configuration option, so that PgBouncer runs its authentication queries only against the `postgres` database. This results in a simpler reconciliation loop with no extra connections required for other databases. Closes: cloudnative-pg#4939 Signed-off-by: Leonardo Cecchi <[email protected]>
|
#8671 is an alternative and simpler implementation of this concept, that doesn't allow the user to change the name of the database where the |
I really like it. We should not need that feature. The goal of the This is already a big improvement. |
|
Closing this as replaced by #8671 |
|
❗ By default, the pull request is configured to backport to all release branches.
|
7 participants
Fixes #1383.
An initial draft implementation to discuss