| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>, pgsql-hackers-win32(at)postgresql(dot)org |
| Subject: | Re: long sql "in" clause crashes server process (8.0 Release) |
| Date: | 2005-01-24 21:21:11 |
| Message-ID: | 25124.1106601671@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> On MingW, you add:
> -Wl,--stack=4194304
> to get 4Mb stack. At least the value increases in the header.
> And I can confirm that doing this fixes the problem and turns it into
> the error message about stack size. (But won't things crash again if I
> increase that one?
Sure. The point is that Postgres doesn't have any way to determine the
allowed stack size, so you have to tell it. Our alternatives here are
(a) to change the default max_stack_depth for Windows, or (b) to make the
platform adhere to the default expectation. (b) looks easier.
> Patch attached.
Will apply.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2005-01-24 21:22:46 | Re: long sql "in" clause crashes server process (8.0 Release) |
| Previous Message | Magnus Hagander | 2005-01-24 21:16:26 | Re: long sql "in" clause crashes server process (8.0 Release) |