| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | 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 13:47:32 |
| Message-ID: | CAB7nPqSGTL_dUU_2+z9LvDDCCtMwKRyi=-A9ggWZ_4QvsmD1mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2016-11-11 14:22:53 | Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |
| Previous Message | jari.kopponen | 2016-11-11 12:12:49 | BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |