Skip site navigation (1) Skip section navigation (2)

Re: long sql "in" clause crashes server process (8.0 Release)

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 (view raw or flat)
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

In response to

pgsql-hackers-win32 by date

Next:From: Merlin MoncureDate: 2005-01-24 20:03:58
Subject: Re: long sql "in" clause crashes server process (8.0 Release)
Previous:From: Merlin MoncureDate: 2005-01-24 19:54:43
Subject: Re: long sql "in" clause crashes server process (8.0 Release)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group