Wed Mar 27 12:17:53 PDT 2013
- Previous message: [Slony1-general] PGRES_FATAL_ERROR ERROR: stack depth limit exceeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Mar 27, 2013 at 1:07 PM, Csaba Nagy <ncslists at googlemail.com> wrote: > Hi all, > > We have here a slony setup where this error is consistently showing up: > > PGRES_FATAL_ERROR ERROR: stack depth limit exceeded > HINT: Increase the configuration parameter "max_stack_depth", after > ensuring the platform's stack depth limit is adequate. > > The line before this error message in the slony logs has ~11MB worth of > text consisting mainly in a long concatenation of: > > ... and log_actionseq <> '...' This was noticed in 2.0.7, reported as bug #264, and fixed: http://www.slony.info/bugzilla/show_bug.cgi?id=264 Essentially, adding an "ORDER BY" to two queries. (See the patches attached to the bug) You'd need to recompile slon, but it shouldn't be necessary to upgrade to an altogether newer version. We did get a positive response that the patch rectified things in 2.0.7, so that seems precisely relevant to your situation.
- Previous message: [Slony1-general] PGRES_FATAL_ERROR ERROR: stack depth limit exceeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list