Обсуждение: Hard max_stack_depth / WIN32_STACK_RLIMIT PostgreSQL Windows Query
Hi all,
I am on a bit of fact-finding mission for a problem we are hitting with PostgreSQL on Windows.
I am unable to start PostgreSQL on windows if I have the max_stack_depth limit greater than 3584kB
DETAIL: “max_stack_depth” must not exceed 3584kB.
Looking at the source code it appears that the maximum stack limit is hard coded as 4194304 bytes for Windows builds. My query is why this number was picked? Is it to do with the maximum size the Windows Kernel will allow? Could I just increase the number and re-compile, or would that break other things?
Paul
Paul Turton <no-2@uber-force.co.uk> writes:
> Looking at the source code it appears that the maximum stack limit is hard coded as 4194304 bytes for Windows builds.
Myquery is why this number was picked? Is it to do with the maximum size the Windows Kernel will allow? Could I just
increasethe number and re-compile, or would that break other things?
A bit of "git blame" archaeology says that that traces back to
commit bf7737a938827608ce79586efe55c642c1a4a7d3
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: Wed Jan 26 21:55:26 2005 +0000
On Windows, set the postmaster executable's stack size to 4MB, so that
it agrees with the default value of max_stack_depth.
So yeah, you could probably increase it in a custom build. However,
I question a bit why you think you need to. IME hardly anyone ever
fools with max_stack_depth, on any platform.
regards, tom lane