Not exactly. We are seeing this on both Windows 7 SP1 and Windows 10 and it started after recent Windows security
updates.
If we manually restart the PostgreSQL service it starts working again but the problem usually comes back after a day or
two.
/Mikael
-----Original Message-----
From: Michael Paquier [mailto:michael.paquier@gmail.com]
Sent: den 15 november 2016 04:10
To: Mikael Wallén <Mikael.Wallen@spark-vision.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: [BUGS] BUG #14423: Fail to connect to DB
On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.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
