| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | "Schuch, Mathias (Mathias)" <mschuch(at)avaya(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14050: "could not reserve shared memory region" in postgresql log |
| Date: | 2016-04-06 06:07:41 |
| Message-ID: | 20160406060741.GA1671244@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Apr 04, 2016 at 08:05:34AM +0000, Schuch, Mathias (Mathias) wrote:
> We use the PostgreSQL setup from EnterpriseDB. There is a McAfee VirisScan Enterprise 8.8 running on the system.
You could try updating to PostgreSQL 9.3.12 and disabling the antivirus
software. I don't have a specific reason to expect those to help, but they're
relatively easy.
In your position, I would next instrument postgres.exe to log a memory map of
the child during pgwin32_ReserveSharedMemoryRegion(). That would show which
DLL created the address space collision.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | yuan_rui1987 | 2016-04-06 06:10:38 | BUG #14067: Wrong result of <select distinct geometry from XXX> |
| Previous Message | yuanrui | 2016-04-06 06:04:08 | Wrong result of <select distinct geometry from XXX> |