zalando / zalando/postgres-operator

Add a user with psql and PGBouncer active

Open
#1,634 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.7.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
  • Are you running Postgres Operator in production? yes
  • Type of issue? question

When trying to add a new user and DB with psql and afterwards trying to access the new DB with the newly created user through the PGBouncer we always receive:

pooler error: unexpected response from login query

And psql tells us:

psql: error: connection to server at "XXXX.triebwork.com", port 32241 failed: ERROR:  unexpected response from login query

I don't understand this error, as I thought, that PGBouncer is using the auth_query to ask postgres about user-permissions...

When trying to connect directly to the DB it works immediately.

How can we dynamically add and delete users and still use the PGBouncer?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are mentioned. Start by reproducing the difference between direct PostgreSQL access and the PgBouncer path, then inspect how auth_query handles users created through psql. Done means documenting a supported way to add and delete users while retaining PgBouncer access.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.