Re: long sql "in" clause crashes server process (8.0 Release)
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Harald Massa" <ghum(at)gmx(dot)net>
- 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:34:05 -0500
- Message-id: <24048(dot)1106595245(at)sss(dot)pgh(dot)pa(dot)us>
"Harald Massa" <ghum(at)gmx(dot)net> writes:
> I issue the following SQL:
> delete from bcachekunde where id_p in (1,2,3,4,6,10,12,13,14,16, [....10740
> more ids...] 90041492, 90721705)
> with the result:
> 2005-01-24 11:35:04 LOG: server process (PID 3776) exited with unexpected
> status 128
Anyone know what status 128 might mean on Windows?
On my non-Windows machine this works fine, but increasing the number of
ID values to 17000 or so causes
ERROR: stack depth limit exceeded
HINT: Increase the configuration parameter "max_stack_depth".
I'm suspicious that either the stack depth detection code doesn't work
at all on Windows, or the default setting of max_stack_depth is in fact
more than the default physical stack size on Windows. Can anyone check?
regards, tom lane
Home |
Main Index |
Thread Index