You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tsegismont , round-robin does not help us with targetServerType=master. Please correct me if I am wrong, but as I understand PgClient doesn't care about the type of the server.
It would be great if PgClient could choose only preferred/required servers (primary, secondary etc. HostRequirement). We cannot correctly use HA Postgres clusters without it. Classic JDBC Driver example is here: MultiHostChooser
Thank you, @vietj . Maybe one day I will start implementing it.
But I believe HA support should work out of the box as part of the vertx-pg-client. It should help the widespread adoption of the PgClient in large projects using Vert.x, Quarkus etc.
Describe the feature
here I saw that we cannot connect to a multi hosts instance of postgres which is mandatory for us.
Can you plan supporting multi hosts connection ?
Use cases
Use case: Support high availbility postgresql instances
As an example, with the classic jdbc driver, we can define this property to connect to our HA postgres instance:
It would be great to be able to do the same with your PgClient by parsing the URI the same way
The text was updated successfully, but these errors were encountered: