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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Mon, 24 Jan 2005 14:57:16 -0500
  • Message-id: <24278(dot)1106596636(at)sss(dot)pgh(dot)pa(dot)us>

"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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group