Re: windows shared memory error

Andrew Dunstan <andrew@dunslane.net> writes:
> We've seen similar things with other Windows file operations, IIRC. What 
> bothers me is that the problem might be precisely because the 1 second 
> sleep between the CloseHandle() call and the CreateFileMapping() call 
> might not be enough due to system load, so repeating the cycle without 
> increasing the sleep period will just repeat the error.

What system load?  This is only called after all the backends are dead.
And surely one CreateFileMapping syscall per second does not materially
contribute to any load that is being caused by something else.
        regards, tom lane