From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | aihongwei <ufo008ahw(at)163(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5131: The pgsql will lost |
Date: | 2009-10-22 13:43:51 |
Message-ID: | 603c8f070910220643k3ba22ff2q5a06ab7669db315a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Oct 21, 2009 at 11:23 PM, aihongwei <ufo008ahw(at)163(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5131
> Logged by: aihongwei
> Email address: ufo008ahw(at)163(dot)com
> PostgreSQL version: 8.0.0
> Operating system: linux x86_64
> Description: The pgsql will lost
> Details:
>
> 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.
>
> example:
> CREATE FUNCTION infinite_recurse() returns int as
> 'select infinite_recurse()' language sql;
> select infinite_recurse();
*scratches head*
Well, you haven't really told us what happens when you do this. Does
it hang up forever? How long did you wait? Does it crash?
The default value for max_stack_depth (NOT stack_max_depth) seems to
be 2MB, so setting the system limit to the same value seems like a bad
idea.
http://www.postgresql.org/docs/current/interactive/runtime-config-resource.html#GUC-MAX-STACK-DEPTH
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-10-22 14:00:22 | Re: BUG #5130: Failed to run initdb:1 |
Previous Message | Savita | 2009-10-22 13:02:11 | BUG #5135: sorting order |