-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Reactive - Support multi hosts connection to Postgres #29348
Comments
/cc @tsegismont, @vietj |
@geoand do you know if it is possible to customize connect options in user code? @mcanzerini as a workaroud, you create the PgPool directly in your application (with your own config options) |
If you are looking for a way to customize the Or maybe it makes sense for users to customize the pool instead? Let me know what you think and I can provide an initial PR showing how this can be done. |
Are there some extensions which do something similar and which I could
inspire from?
|
None of the datasource extensions do this IIRC. I'll open a draft tomorrow to show you what I have in mind (which is in line with the way other extensions like Jackson for example handle such cases) |
Cool, thanks
|
If you do this, make sure to make the |
@tsegismont #29397 is what I have in mind (cc @gsmet for awareness as well). |
Hi guys, any update on this ? |
Hopefully soon :) |
Great, thanks for your time 🙏 |
Provide a way for users to customize PgPool creation
Description
I need to connect to multiple postgres hosts with hibernate-reactive.
With the classic jdbc driver, we can define this property to connect to our HA postgres instance:
quarkus.datasource.jdbc.url=jdbc:postgresql://my.host-1.com,my.host-2.com,my.host-3.com:5432/myDB
But here I saw that the vert.x PgClient does not support multi host connections directly in connection URI.
I created an issue in vertx-sql-client here and a developer said me that it would be already possible by using the PgConnectOptions and a PgPool.
Can you support connection pool to multi hosts through your implementation ?
The text was updated successfully, but these errors were encountered: