From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
Cc: | pgsql-hackers-win32(at)postgresql(dot)org |
Subject: | Re: long sql "in" clause crashes server process (8.0 Release) |
Date: | 2005-01-24 19:57:16 |
Message-ID: | 24278.1106596636@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers-win32 |
"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> C:\msys\1.0\local\pgsql\bin>"c:\Program Files\Microsoft Visual
> Studio\VC98\Bin"\dumpbin /headers pos
> tmaster.exe | grep stack
> 200000 size of stack reserve
> 1000 size of stack commit
Hmm, are those in bytes? The default value of max_stack_depth is 2048
(kilobytes), which really means that we are assuming a physical stack
limit of 3Mb or more, because the max_stack_depth check isn't exact.
Can we increase that setting during the Windows build? I'd like to see
it set to 4Mb if possible.
BTW, what's the difference between "stack reserve" and "stack commit"?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-01-24 20:03:58 | Re: long sql "in" clause crashes server process (8.0 Release) |
Previous Message | Merlin Moncure | 2005-01-24 19:54:43 | Re: long sql "in" clause crashes server process (8.0 Release) |