"Magnus Hagander" <mha@sollentuna.net> writes:
> There is the issue with shared mem on Win2003 that came up the other
> day. I don't think it's a general error, but rather something
> environment specific. (I've had several reports of ppl with fairly large
> databases in production on win2003 that don't have this problem).
I doubt that size of database has anything at all to do with this.
Is there a way to determine current end of ordinary memory in Windows?
(Something akin to sbrk(0) on Unix.) It would be interesting to get the
complainant to try it with some code added that prints out the memory
end address both just before the postmaster creates the shmem segment,
and just before the child process tries to attach to it. (Maybe these
are the same place in the code, don't recall for sure.)
regards, tom lane