Tom Lane wrote:
> Frank Featherlight <dirtydude@gmail.com> writes:
>> while reading your thread two things come to mind, I have installed:
>> Registry Mechanic ( http://www.pctools.com/registry-mechanic )
>> Tune-Up Utilities ( http://www.tune-up.com/products/tuneup-utilities )
>> Any of these two might cause the problem aswell in your opinion?
>
> Damifino, I'm not a Windows person. But I'd suggest methodically
> removing each and every bit of non-default software you've got,
> to see if you can find one that causes the failure. We know that
> the failure does not occur on stock Windows or with most popular
> add-ons, so unusual add-ons deserve a close look.
I wonder if it would help to reserve the address space for the shared
memory block earlier. We could pass the address and size of the shared
memory block as extra arguments to the backend, and reserve it before
doing anything else. There's even a function called VirtualAllocEx, that
postmaster could call right after CreateProcess to reserve the address
space on behalf of the child process.
Of course, none of this helps if the culprit is a DLL or a 3rd party
program that allocates the adress space immediately at CreateProcess.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
