Re: BUG #14423: Fail to connect to DB

Some additional info.
It seems as if this is related to F-Secure and/or anti-virus software in general. A colleague tried to temporarily disable F-Secure and then the errors stopped. However as soon as he enabled F-Secure again the error messages started filling the PostgreSQL logs.
However I have also seen the same error messages on a virtual machine running Windows 10 Pro with the latest Windows updates and there I am not running F-Secure. I am running Windows Defender though.

/Mikael

-----Original Message-----
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
Sent: den 15 november 2016 04:10
To: Mikael Wallén <Mikael(dot)Wallen(at)spark-vision(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #14423: Fail to connect to DB

On Mon, Nov 14, 2016 at 1:07 AM, <mikael(dot)wallen(at)spark-vision(dot)com> wrote:
> Errors saying "could not fork new process for connection: No error"
> are also occurring when using pgadminIII as well as psql. Everything
> worked well before the recent Windows updates. Is this somehow related
> to changes in ASLR (address space layout randomization) and if so, is
> there any workaround?

Let me guess: you are seeing that since you updated to Win7 SP1?
That's not the first complain in the area...
--
Michael