Re: BUG #14423: Fail to connect to DB

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: mikael(dot)wallen(at)spark-vision(dot)com
Cc: PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14423: Fail to connect to DB
Date: 2016-11-15 03:10:00
Message-ID: CAB7nPqS4jMFitRQgkz7jKKUD5uVmDuEndOf2s1ouS8KcXbk_sw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message hikkis21c 2016-11-15 06:38:34 BUG #14424: install fail
Previous Message Vik Fearing 2016-11-15 01:07:48 Re: DOS-style line endings in .pgpass