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

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Re: BUG #14050: "could not reserve shared memory region" in postgresql log
Date: 2016-04-06 22:41:09
Message-ID: 57059085.3040002@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2016-04-07 01:59:29 Re: BUG #14067: Wrong result of <select distinct geometry from XXX>
Previous Message David Gould 2016-04-06 20:35:43 Re: PosgreSQL backend process crashed with signal 9