News for hackers. Stuff that matters.

A comment on Why we built yet another Postgres connection pooler. Parent comment

Re:Why we built yet another Postgres connection pooler by SahAssar on Tuesday July 07, 2026 @07:41PM (#48825520)
> But I don’t think I would want to create a real database user for every version of the app.

Why not? Database users are (usually) not expensive, and with groups you can give access to a group you just add the user to.

Adding this logic to the connection pooler seems more complicated.

[ Parent | on HN ]
Re:Why we built yet another Postgres connection pooler by drdexebtjl on Tuesday July 07, 2026 @09:02PM (#48826161)
Because it means connecting to the database to provision a new user on every deploy.

Also because it doesn’t really concern the database, it concerns the pooler.

Connection poolers already maintain multiple pools, it would not be complicated at all.

[ Parent | on HN ]