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

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

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:22:46
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE4766DE@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackers-win32
>> 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.

Agreed. Just wanted to be sure. If someone needs it, they can always
tweak that number int he Makefile and rebuild from source.

//Magnus

Responses

pgsql-hackers-win32 by date

Next:From: Tom LaneDate: 2005-01-24 21:38:41
Subject: Re: long sql "in" clause crashes server process (8.0 Release)
Previous:From: Tom LaneDate: 2005-01-24 21:21:11
Subject: Re: long sql "in" clause crashes server process (8.0 Release)

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