"Trevor Talbot" <quension@xxxxxxxxx> writes: > On 8/23/07, Magnus Hagander <magnus@xxxxxxxxxxxx> wrote: >> Not that wild a guess, really :-) I'd say it's a very good possibility - >> but I have no idea why it'd do that, since all backends load the same >> DLLs at that stage. > Not a valid assumption; you can't rely on consistent VM space among > multiple [non-cloned] processes without a serious amount of effort. I'm not sure if you have a specific technical meaning of "clone" in mind here, but these processes are all executing the identical executable, and taking care to map the shmem early in execution *before* they load any DLLs. So it should work. Apparently, it *does* work for awhile for the OP, and then stops working, which is even odder. > I gather postgres depends on it being at the same address, and fixing > that isn't trivial? That's correct, and not having to change it is not negotiable --- finding a way to make this work was one of the gating factors that made it practical to have a Windows port at all. If you've got a specific suggestion for making it more reliable, we're all ears. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/