Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
2 posts • Page 1 of 1
Our appliction performs several very long processes to our database and everything was running just fine until a connection timeout issue appeared. Our application records the initial and final times and also shows the total time that the process takes. Because of the connection timeout issue I set the connection timeout to zero and I have noticed that the processes take significantly less time now. Is this a normal behavior?
If the connection timeout parameter value is not equal to zero, a separate thread is created for establishing a database connection. In case the connection timeout parameter value is equal to zero, an additional thread is not created. This might be the reason of performance increase you observe.