Florian Weimer wrote: > * Magnus Hagander: > >> Oh, that's interesting. That's actually a sideeffect of us increasing >> the stack size for the postgres.exe executable in order to work on other >> things. By default, it burns 1MB/thread, but ours will do 4MB. Never >> really thought of the problem that it'll run out of address space. >> Unfortunately, that size can't be changed in the CreateThread() call - >> only the initially committed size can be changed there. > > Windows XP supports the STACK_SIZE_PARAM_IS_A_RESERVATION flag, which > apparently allows to reduce the reserved size. It might be better to do > this the other way round, though (leave the reservation at its 1 MB > default, and increase it only when necessary).
It does, but we still support windows 2000 as well. I think it's better to use a different method altogether - one not using one thread per child. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
