Re: BUG #14050: "could not reserve shared memory region" in postgresql log
От | Schuch, Mathias (Mathias) |
---|---|
Тема | Re: BUG #14050: "could not reserve shared memory region" in postgresql log |
Дата | |
Msg-id | C17BDE1BC28A314E927010993FFBA7F23A33555A@AZ-FFEXMB02.global.avaya.com обсуждение исходный текст |
Ответ на | Re: BUG #14050: "could not reserve shared memory region" in postgresql log (Noah Misch <noah@leadboat.com>) |
Ответы |
Re: BUG #14050: "could not reserve shared memory region" in
postgresql log
|
Список | pgsql-bugs |
We use the PostgreSQL setup from EnterpriseDB. There is a McAfee VirisScan = Enterprise 8.8 running on the system. -----Urspr=FCngliche Nachricht----- Von: Noah Misch [mailto:noah@leadboat.com]=20 Gesendet: Sonntag, 3. April 2016 22:58 An: Schuch, Mathias (Mathias) <mschuch@avaya.com> Cc: pgsql-bugs@postgresql.org Betreff: Re: BUG #14050: "could not reserve shared memory region" in postgr= esql log On Tue, Mar 29, 2016 at 09:38:04AM +0000, mschuch@avaya.com wrote: > PostgreSQL version: 9.3.5 > Operating system: Windows 7 > 2016-03-16 14:45:28 EST LOG: could not reserve shared memory region > (addr=3D0000000001BB0000) for child 000000000000047C: error code 487 > 2016-03-16 14:45:28 EST LOG: could not fork autovacuum worker=20 > process: A blocking operation was interrupted by a call to WSACancelBlock= ingCall. >=20 > I read in the release notes that this issue should be solved with=20 > 9.3.4 but with 9.3.5 it isn't. We had not seen this on Windows 7. From where did you download the Postgre= SQL binaries, or with which tools did you build them? Which antivirus and/= or anti-malware software does this system use?
В списке pgsql-bugs по дате отправления: