Re: Server process exited with unexpected status 128. - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Server process exited with unexpected status 128.
Date
Msg-id 28493.1127746877@sss.pgh.pa.us
Whole thread Raw
In response to Re: Server process exited with unexpected status 128.  ("Dave Page" <dpage@vale-housing.co.uk>)
Responses Re: Server process exited with unexpected status 128.
List pgsql-hackers
"Dave Page" <dpage@vale-housing.co.uk> writes:
>> [mailto:pgsql-hackers-owner@postgresql.org] 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.postgresql.org/pgsql-committers/2005-01/msg00386.php

D'oh.  Well, at the very least we have a documentation issue here.

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 ---
you're assumed to know what you are doing if you change it.)
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Server process exited with unexpected status 128.
Next
From: Greg Stark
Date:
Subject: Re: roundoff problem in time datatype