-
Notifications
You must be signed in to change notification settings - Fork 205
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
Single pool for multiple databases #806
Comments
I just noticed that we can have a shard per tenant and that would fix the issue where we can't limit the connections overall but these are not possible to be added through the pgcat admin api which would mean that we need to manually add them to the |
Hey, I just read the issue. I see you've already kind of found the answer. Although both things seem 'doable' there is no way of having 'dynamic db names' on pools neither adding new pool config through admin api (which is mostly for statistics and a few commands). Either way, you can leverage pgcat live configuration reloading functionality to achive what you want. The only piece left is a simple service that handles the config changes, rewrite the config using some kind of templating system and signal pgcat to reload the configuration, that would be the way I'd do it. Also, bear in mind that you have to execute SET SHARD TO 'SHARD_NUMBER'; before each query/transaction for this to work. |
Thanks for the reply, we are working with Prisma so we can't really alter the SQL query in there so I'm affraid this won't be an option. If you have any other ideas that would be great, or other tools that could work as I'm not finding anything 🥲 |
There is also a possibility, If you can 'annotate' with comments your query, pgcat can extract that information and do the sharding selection. |
@nealoke @rvsoni, we have the same challenges, multiple tenants each has own DB with username/pwd, and multiple tenants share a DB cluster. We are currently looking to make it work with PgCat, PgBouncer or Supavisor. (in that order) On top there are a few less known pooler (at least to me) odyssey @rvsoni, why did you try to make it work with pgcat, hence your pr? It seems there are quite a few options out there already. |
Hello @Vad1mo This fix works as you described: set one Pool on pgcat with Auth_quey config and make proxy = true (in my PR). This would dynamically create a pool of connections for each user/db on the same cluster. From the client side, you need to maintain just only one pool to pgcat and keep login using your user/pass map to database (user name and database name must need to be same) Ravi |
@Vad1mo I'm not that familiar with all that is related to revers proxies and half of what the pgcat tries to do 😅. So I read your comment and also looked at the messages in the #855 and the PR but can't seem to understand how this would solve my issue or how I would even need to implement this. I don't directly see the link to how I can map |
The most important point this discussion misses is the need for an authentication configuration on PgCat based on an You need to set a Pool on pgcat points to a Postgre cluster with auth method of This query returns a password from the PostgreSQL cluster for each tenant user you try to authenticate over the pgcat pool setting. This allows you to connect to many databases on one pgcat pool setting. Refer https://github.com/rvsoni/pgcat/blob/main/pgcat.proxy.toml and https://hub.docker.com/r/rvsoni/pgcat docker image to test this dynamic connection pool creation for all tenant database, |
Context
We have a multi-tenant SaaS setup where each tenant has a database in a managed database cluster (Scaleway/DigitalOcean/...). Currently we are using a single cluster. The goal for us for using pgcat is that we can limit the amount of connections to our database cluster as the cluster has a limited amount of connections available.
Problem
As we have one cluster we essentially only need one pgcat pool, the only issue I'm bouncing against is that it is impossible for us to allow multiple different databases inside a single pool. And if I were to create separate pools for each tenant, then the implementation with pgcat has no benefit as we can't limit the connections as a while towards the database cluster. A simple example:
Potential solution
It would be awesome if we could allow a regex pattern for which databases should connect to a certain pool, in that way we could say that
tenant-1
untiltenant-50
should connect to pool 1 andtenant-51
untiltenant-100
should connect to pool 2.Or is all this unneeded and am I missing something?
The text was updated successfully, but these errors were encountered: