Re: Re: BUG #14050: "could not reserve shared memory region" in postgresql log - Mailing list pgsql-bugs

From John R Pierce
Subject Re: Re: BUG #14050: "could not reserve shared memory region" in postgresql log
Date
Msg-id 57059085.3040002@hogranch.com
Whole thread Raw
In response to Re: BUG #14050: "could not reserve shared memory region" in postgresql log  ("Schuch, Mathias (Mathias)" <mschuch@avaya.com>)
Responses Re: BUG #14050: "could not reserve shared memory region" in postgresql log
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: David Gould
Date:
Subject: Re: PosgreSQL backend process crashed with signal 9
Next
From: David Rowley
Date:
Subject: Re: BUG #14067: Wrong result of

Соглашаюсь с условиями обработки персональных данных