Gary Doades <gpd@gpdnet.co.uk> writes:
> AFAIK Win32 does not care where in private process address space the
> "shared memory" segment is. It can be mapped to different addresses in
> different processes and still share the same physical address space.
> This is why Win32 puts the private shared address anywhere in its own
> address space, because it doesn't matter.
Win32 may not care, but we do. The shared memory segment must be mapped
at the same address in every backend.
> If you try to force it to any particular private process address you may
> fail as you don't always know where program code (DLLs etc.) may be loaded.
This is (or ought to be) irrelevant, because we are only talking about
instances of a single executable.
regards, tom lane
