From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Mikael Wallén <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-16 17:26:52 |
Message-ID: | CAB7nPqRu_CtPC3z_ybdOYYw++Zu9DR4=kWD9nN4Uy6CCopkv7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Nov 16, 2016 at 1:48 AM, Mikael Wallén
<Mikael(dot)Wallen(at)spark-vision(dot)com> wrote:
> 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.
Interesting. So would Windows 10 be enforcing Windows Defender or a
virus scanner to be enabled? This OS shines a lot in updating settings
forcibly with its automatic updates, sometimes without caring about
what the user may have changed in the past.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Sandeep Thakkar | 2016-11-17 05:57:18 | Re: BUG #14425: Installation issues |
Previous Message | Tom Lane | 2016-11-16 17:26:37 | Re: Index file got removed |