Yes, you read it right, Npgsql wasn't using connection pool when running under Mono!!
The problem seemed to be that Npgsql was using one key to get a connection to pool and another one to return it back.
The issue is that although it is wrong, those two values were supposed to be the same.
You can see here and here bug reports about it.
The problem seemed to be that Npgsql was using one key to get a connection to pool and another one to return it back.
The issue is that although it is wrong, those two values were supposed to be the same.
You can see here and here bug reports about it.
Well, the fix is already on cvs, so if you were using Npgsql on Mono, you should definitely give it a try so you can see if your code works ok.
Sorry for this problem.
Later I will bring a full analysis of what can be the problem.
Comments
I mean, maybe you should fix on Mono upstream, not in Npgsql downstream.
Yeah. I think it may be an issue with Mono. But anyway, Npgsql code was also wrong. It was using Connection.ConnectionString in one place and Connector.ConnectionString in other.
I will be adding a post about this problem soon.
Brightly coloured polo shirts can make you look like a Day-glo dirigible.
Wonderful!You can find the father who desire fashionable, intellectual polo shirt simultaneously