> -----Original Message----- > From: pgsql-general-owner@xxxxxxxxxxxxxx [mailto:pgsql-general- > owner@xxxxxxxxxxxxxx] On Behalf Of Leif Biberg Kristensen > Sent: Thursday, August 18, 2011 6:49 AM > To: pgsql-general@xxxxxxxxxxxxxx > Subject: Re: max_stack_depth error, need suggestion > > On Thursday 18. August 2011 12.39.31 AI Rumman wrote: > > I am using Postgresql 9.0.1 in Centos 5. > > > > Yesterday, I got the error inlog: > > > > 2011-08-16 10:57:34 EDT [3868]: [1-1] user=vcrm,db=vtigercrm504 > ERROR: > > stack depth limit exceeded > > 2011-08-16 10:57:34 EDT [3868]: [2-1] user=vcrm,db=vtigercrm504 HINT: > > Increase the configuration parameter "max_stack_depth", after > ensuring the > > platform's stack depth limit is adequate. > > > > > > I found that I need to increase max_stack_depth. But doc says that it > is a > > bit risky increasing it. > > > > Could any one please suggest me what the maximum safe value I may set > in my > > environment? > > > > My Server RAM is 32 GB. > > That error message is usually caused by an infinite recursion. Slony can also cause this to happen (at least it could - I'm not sure if it still does) - it wasn't from infinite recursion though. I used to have to set that higher for some of my clusters. They may have fixed the query that was causing that to happen though. Brad. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
