From: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, jari(dot)kopponen(at)patria(dot)fi |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |
Date: | 2016-11-11 14:22:53 |
Message-ID: | 13f1773c-5e0d-72c6-a298-c483c458e051@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 11/11/2016 14:47, Michael Paquier wrote:
> On Fri, Nov 11, 2016 at 9:12 PM, <jari(dot)kopponen(at)patria(dot)fi> wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 14419
>> Logged by: jari kopponen
>> Email address: jari(dot)kopponen(at)patria(dot)fi
>> PostgreSQL version: 9.4.4
>> Operating system: Windows 7 Professional, 64 bit SP 1
>> Description:
>>
>> After we installed kb3177467 (Servicing stack update for Windows 7 SP1 and
>> Windows Server 2008 R2 SP1: September 20, 2016) windows update, we faced
>> problems with database connections. In postgresql there is log entries
>> "could not reserve shared memory region (addr:xxx) for child(yyy): error
>> code 487. This seems to be quite similar problem than described in : BUG
>> #14050.
>
> From where are those builds? Is ASLR enabled? I saw patterns of broken
> shared memory with Win 2k8 R2 because of that.
>
FWIW, there was 3 reports for this issue on french board in the last few
days (including pg 9.3.3 and 9.5.5), I think all of them on W7.
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
From | Date | Subject | |
---|---|---|---|
Next Message | rotten | 2016-11-11 22:06:57 | BUG #14420: Parallel worker segfault |
Previous Message | Michael Paquier | 2016-11-11 13:47:32 | Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |