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 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
