On Wed, Oct 21, 2009 at 11:23 PM, aihongwei <ufo008...@163.com> wrote: > > The following bug has been logged online: > > Bug reference: 5131 > Logged by: aihongwei > Email address: ufo008...@163.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
