Tue May 30 12:40:28 PDT 2006
- Previous message: [Slony1-general] stack depth limit exceeded
- Next message: [Slony1-general] stack depth limit exceeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, May 30, 2006 at 12:29:41PM -0700, Wayne Conrad wrote: > has a "where log_actionseq not in (...)" clause with about 320,000 > numbers in it, which is what is making postgres cranky. Sort of. If I'm not mistaken, that setting is in the postgresql.conf file, and it's measured in KB. You can increase it. I believe it requires a restart of the postmaster to take effect, but check the docs. Of course, that might just be masking the symptom of a serious bug. A -- Andrew Sullivan | ajs at crankycanuck.ca "The year's penultimate month" is not in truth a good way of saying November. --H.W. Fowler
- Previous message: [Slony1-general] stack depth limit exceeded
- Next message: [Slony1-general] stack depth limit exceeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list