Indeed those messages appear when the client closes the socket connection only.
Npgsql has connection pooling and if the app domain is unloaded and
there are connections in the pool, those connections don't get a
chance to have the Close message sent to backend server.
So, even when you are corre
On Tue, 08 Mar 2011 11:30:10 +0800, Craig Ringer wrote:
On 08/03/11 02:49, Piotr Czekalski wrote:
I've checked and verified that all connections are closed within the
code, what's more, the problem has appeared just as I've moved
server
from Fedora Linux x86_64 running Postgres 8.4.2 to the Wi
On 08/03/11 02:49, Piotr Czekalski wrote:
> I've checked and verified that all connections are closed within the
> code, what's more, the problem has appeared just as I've moved server
> from Fedora Linux x86_64 running Postgres 8.4.2 to the Windows and 9.0.3
> (details above) thus I conclude this
Hello there,
I'm getting regular Postgres log entries with the following error:
2011-03-07 01:00:01 CET LOG: could not receive data from client: No
connection could be made because the target machine actively refused it.
2011-03-07 01:00:01 CET LOG: unexpected EOF on client connection
They a
