Re: BUG #5131: The pgsql will lost - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #5131: The pgsql will lost
Date
Msg-id 29538.1256220401@sss.pgh.pa.us
Whole thread Raw
In response to BUG #5131: The pgsql will lost  ("aihongwei" <ufo008ahw@163.com>)
List pgsql-bugs
"aihongwei" <ufo008ahw@163.com> writes:
> In x86_64 platform,
> I input command "ulimit -s 2048" to limit the stack size.Then I startup the
> server,and when i do some recursion operation, the pgsql will lost in some
> time.
> It seems that The stack_max_depth does work.

If you read the description of that setting, you will notice that it
recommends leaving a safety margin of at least one megabyte between the
kernel ulimit setting and the max_stack_depth value.  You have left a
safety margin of zero.  A crash is unsurprising.

More recent versions of Postgres are able to check whether
max_stack_depth has a safe value relative to ulimit -s, but 8.0 just
believes whatever you tell it.

BTW, are you *really* using 8.0.0?  If so please update.  The current
bugfix release in that series is 8.0.22.

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Savita"
Date:
Subject: BUG #5135: sorting order
Next
From: Robert Haas
Date:
Subject: Re: BUG #5132: Invalid Function