From: =?utf-8?B?RXJ0YW4gS8O8w6fDvGtvxJ9sdQ==?= <ertan.kucukoglu@1nar.com.tr>
To: "'Thomas Kellerer'" <spam_eater@gmx.net>,
	<pgsql-admin@postgresql.org>
References: <007601d27887$736d80c0$5a488240$@1nar.com.tr>
 <o6f9bl$kav$1@blaine.gmane.org>
In-Reply-To: <o6f9bl$kav$1@blaine.gmane.org>
Subject: Re: Failed to set up event for socket: error code 10038
Date: Fri, 27 Jan 2017 15:51:46 +0300
Message-ID: <008c01d2789c$1e19bc00$5a4d3400$@1nar.com.tr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQGFLjc2OFYsSBaGPk+Jh+Is32ym4QH5rZL5odcNTeA=
Content-Language: tr
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

> > Ertan K=C3=BC=C3=A7=C3=BCko=C4=9Flu schrieb am 27.01.2017 um 11:23:
> > I read a FATAL marked line in postgresql log file at exact same second:
> > 2017-01-27 12:47:41 +03 FATAL:  failed to set up event for socket:=20
> > error code 10038
> >=20
> > Application is self-closing upon receiving such error. I instantly=20
> > re-run it (to continue my code tests) and sometimes it is 3-4 times=20
> > until I can get my application running.
> >=20
> > I am using latest version of Devart Universal Database Access=20
> > Components
> > (UniDAC) for performing database operations. As far as I know, these=20
> > components make direct connection to PostgreSQL. Nothing in between=20
> > like ODBC or anything. If that is relevant.
> >=20
> > When I was investigating my problem, I also read following lines in=20
> > the postgresql log file:
> > 2017-01-27 12:22:34 +03 LOG:  using stale statistics instead of=20
> > current ones because stats collector is not responding
> > 2017-01-27 12:27:35 +03 LOG:  using stale statistics instead of=20
> > current ones because stats collector is not responding
> > 2017-01-27 12:29:51 +03 LOG:  using stale statistics instead of=20
> > current ones because stats collector is not responding
> > 2017-01-27 12:30:51 +03 LOG:  using stale statistics instead of=20
> > current ones because stats collector is not responding
> > 2017-01-27 12:32:35 +03 LOG:  using stale statistics instead of=20
> > current ones because stats collector is not responding
> >=20
> > My questions are:
> > 1- I understand that PostgreSQL is closing the connection. What may=20
> > cause for such a connection error, and how to solve it?
> > 2- These "stale statistics" messages in log file, are they anything=20
> > important? Is there a way to stop them being logged because they seem=20
> > to grow log file.
>
>=20
> Try to disable your Anti-Virus for a test.=20
>=20
> If things then work, configure your Anti-Virus to not scan the Postgres d=
ata directory and to not check postgres.exe
>=20
> Thomas

Disabling Anti-Virus did not work for me. I continue to have connection pro=
blems.


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin