Re: Re: BUG #14050: "could not reserve shared memory region" in postgresql log

On 4/6/2016 2:07 AM, Schuch, Mathias (Mathias) wrote:
>> 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. 
>
> 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. 

by 'instrument' I believe he meant add appropriate logging statements to
the source code, and recompile postgres.  not an easy undertaking for an
end user.



--
john r pierce, recycling bits in santa cruz