Repository navigation
Add support for automatic pool (similar to pgbouncer) #362
Description
Is your feature request related to a problem? Please describe.
For some applications, it may not be possible to list all databases the application can connect to (for instance when each customer has his own database). For these, it's better to use a feature similar to the automatic pool in pgbouncer, cf. https://www.pgbouncer.org/config.html section databases.
Describe the solution you'd like
Be able to describe an automatic pool generator in the configuration.
Describe alternatives you've considered
None known
Additional context
None
Reacted by Rasmus Hansen, Hellyson Rodrigo Parteka, David Montague, Andrew Jackson, mismaah, Ivan Strelkov, Vadim Bauer and AmythD
Activity
levkk commentedon Mar 14, 2023
Hi there,
I've never used that feature of PgBouncer. Could you give me an example of how it works?
Thanks!
pinaraf commentedon Mar 14, 2023
Hi
In pgbouncer.ini:
When a client connects to the bouncer and asks for the database demo, it will spawn a new pool, named demo, for the database demo on my.server.org:5432.
If the client disconnects, the pool will remain "forever" or until autodb_idle_timeout is reached.
The usual server_idle_timeout and server_lifetime rules apply.
Regards
adriangb commentedon Jan 31, 2024
+1 for this feature. I specifically need users wildcards.
AndrewJackson2020 commentedon Apr 26, 2024
+1 for this feature, without it there ends up being a lot of boilerplate and manual upkeep in an environment with a large number of databases and users.
strelkovia commentedon May 31, 2024
Hi
+1 for this feature
bharling commentedon Aug 14, 2024
Hallo! +1 from me too please, this would be really useful
giovanniborella commentedon Aug 30, 2024
+1 much needed for use-case
rvsoni commentedon Nov 17, 2024
I implemented #855 to have PGBouncer pool proxy implementation.
Try this PR #855 or you can use my Repo @rvsoni/pgcat with fix,