Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log.
От | Michael Paquier |
---|---|
Тема | Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |
Дата | |
Msg-id | CAB7nPqSGTL_dUU_2+z9LvDDCCtMwKRyi=-A9ggWZ_4QvsmD1mw@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. (jari.kopponen@patria.fi) |
Ответы |
Re: BUG #14419: DB connections fails with "could not reserve
shared memory region" in postgresql log.
Re: BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log. |
Список | pgsql-bugs |
On Fri, Nov 11, 2016 at 9:12 PM, <jari.kopponen@patria.fi> wrote: > The following bug has been logged on the website: > > Bug reference: 14419 > Logged by: jari kopponen > Email address: jari.kopponen@patria.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
В списке pgsql-bugs по дате отправления: