Connection Pooling for databases running on multiple machine
-
- Posts: 4
- Joined: Tue 01 Dec 2009 16:54
Connection Pooling for databases running on multiple machine
Does dotConnect support connection pooling to multiple database instances? The configuration is postgresql running on two machines in master-slave configuration utilizing Slony-I for replication. A dotConnect entity pointing to the master, and on failover, the connection goes to the next database connection, on the slave computer. Also, does dotConnect have a mechanism for a failed master to rejoin the cluster as the new slave, without a manual configuration change? I could handle this in code with two entities, but this would be unnecessary if dotConnect did this automatically. I also could handle this with a separate load-balancer as long as I wrote a script on the postgresql host to kill its connection on a postgresql failure. It dotConnect cannot do these things, then consider this topic as a new feature request.
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
Thank you for your suggestion. At the moment, these features are not available in dotConnect for PostgreSQL.
We will investigate the possibility of implementing local failover support and the possibility of re-connecting to a slave server when the master one is not accessible.
As for the failed master re-joining the cluster as a slave, could you please specify what support for this is supposed on the client side? This functionality seems to be in responsibility of the replication system, not the data provider.
We will investigate the possibility of implementing local failover support and the possibility of re-connecting to a slave server when the master one is not accessible.
As for the failed master re-joining the cluster as a slave, could you please specify what support for this is supposed on the client side? This functionality seems to be in responsibility of the replication system, not the data provider.
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
We have implemented the local failover feature. It will be available in the nearest build of dotConnect for PostgreSQL, which we plan to release in several days.
To enable local failover, one should set the PgSqlConnection.LocalFailover property to true. The PgSqlConnection.ConnectionLost event can be used to subscribe for the event raised when the connection is lost.
To enable local failover, one should set the PgSqlConnection.LocalFailover property to true. The PgSqlConnection.ConnectionLost event can be used to subscribe for the event raised when the connection is lost.
-
- Devart Team
- Posts: 1710
- Joined: Thu 03 Dec 2009 10:48
We have released the new 5.0.69 version of dotConnect for PostgreSQL where these changes are available. The new build can be downloaded from
http://www.devart.com/dotconnect/postgr ... nload.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/
For more information about the fixes and improvements available in dotConnect for PostgreSQL 5.0.69, please refer to
http://www.devart.com/forums/viewtopic.php?t=19795
http://www.devart.com/dotconnect/postgr ... nload.html
(the trial version) or from Registered Users' Area (for users with active subscription only):
http://secure.devart.com/
For more information about the fixes and improvements available in dotConnect for PostgreSQL 5.0.69, please refer to
http://www.devart.com/forums/viewtopic.php?t=19795