Tom Lane wrote:
Is it sensible to try to prevent people from raising the GUC variable
higher than the platform will allow? It seems we can know the limit on
Windows, but on most other platforms I don't think there's any good way
to find it out. (Which is why max_stack_depth is a SUSET variable
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> Sent: 26 September 2005 16:01
> To: Dave Page
> Cc: Андрей Репко; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Server process exited with unexpected
> status 128.
>
> "Dave Pa
"Dave Page" writes:
>> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
>>> max_stack_depth = 65536 # min 100, size in KB
>>
>> Hmm, maybe this is the problem. Are we sure Windows will
>> allow a 64M stack?
> Looks like we used 4MB in the backend by default:
> http://archives.po
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
> Sent: 26 September 2005 15:47
> To: Андрей Репко
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] Server process exited with unexpected
> status 12
[ looking again... ]
=?Windows-1251?Q?=C0=ED=E4=F0=E5=E9_=D0=E5=EF=EA=EE?= <[EMAIL PROTECTED]>
writes:
> max_stack_depth = 65536 # min 100, size in KB
Hmm, maybe this is the problem. Are we sure Windows will allow a 64M stack?
regards, tom lane
=?Windows-1251?Q?=C0=ED=E4=F0=E5=E9_=D0=E5=EF=EA=EE?= <[EMAIL PROTECTED]>
writes:
> When I try to execute the next SQL statement, sever was crashed:
> DELETE FROM ma_data WHERE id in (-1,212803,. );
> ... - is 500k text like id separated by ",". Its about 10 values.
I wouldn't be too s
Hello pgsql-hackers,
When I try to execute the next SQL statement, sever was crashed:
DELETE FROM ma_data WHERE id in (-1,212803,. );
... - is 500k text like id separated by ",". Its about 10 values.
Run from pgplsql function, like EXECUTE st;.
postgresql-2005-09-25_00.log:
200
