pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ertan Küçükoğlu <ertan.kucukoglu@1nar.com.tr>
To: 'Thomas Kellerer' <spam_eater@gmx.net>
To: pgsql-admin@postgresql.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> (raw)
In-Reply-To: <o6f9bl$kav$1@blaine.gmane.org>
References: <007601d27887$736d80c0$5a488240$@1nar.com.tr>
	<o6f9bl$kav$1@blaine.gmane.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

> > Ertan Küçükoğlu 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: 
> > error code 10038
> > 
> > Application is self-closing upon receiving such error. I instantly 
> > re-run it (to continue my code tests) and sometimes it is 3-4 times 
> > until I can get my application running.
> > 
> > I am using latest version of Devart Universal Database Access 
> > Components
> > (UniDAC) for performing database operations. As far as I know, these 
> > components make direct connection to PostgreSQL. Nothing in between 
> > like ODBC or anything. If that is relevant.
> > 
> > When I was investigating my problem, I also read following lines in 
> > the postgresql log file:
> > 2017-01-27 12:22:34 +03 LOG:  using stale statistics instead of 
> > current ones because stats collector is not responding
> > 2017-01-27 12:27:35 +03 LOG:  using stale statistics instead of 
> > current ones because stats collector is not responding
> > 2017-01-27 12:29:51 +03 LOG:  using stale statistics instead of 
> > current ones because stats collector is not responding
> > 2017-01-27 12:30:51 +03 LOG:  using stale statistics instead of 
> > current ones because stats collector is not responding
> > 2017-01-27 12:32:35 +03 LOG:  using stale statistics instead of 
> > current ones because stats collector is not responding
> > 
> > My questions are:
> > 1- I understand that PostgreSQL is closing the connection. What may 
> > cause for such a connection error, and how to solve it?
> > 2- These "stale statistics" messages in log file, are they anything 
> > important? Is there a way to stop them being logged because they seem 
> > to grow log file.
>
> 
> Try to disable your Anti-Virus for a test. 
> 
> If things then work, configure your Anti-Virus to not scan the Postgres data directory and to not check postgres.exe
> 
> Thomas

Disabling Anti-Virus did not work for me. I continue to have connection problems.




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



view thread (3+ messages)

Message-ID: <008c01d2789c$1e19bc00$5a4d3400$@1nar.com.tr>
Permalink:  ../008c01d2789c$1e19bc00$5a4d3400$@1nar.com.tr/
Also on:    postgresql.org/message-id/008c01d2789c$1e19bc00$5a4d3400$@1nar.com.tr

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ertan.kucukoglu@1nar.com.tr, spam_eater@gmx.net
  Subject: Re: Failed to set up event for socket: error code 10038
  In-Reply-To: <008c01d2789c$1e19bc00$5a4d3400$@1nar.com.tr>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox