Tue Sep 13 22:43:34 PDT 2005
- Previous message: [Slony1-general] "realloc() - Cannot allocate memory" errors
- Next message: [Slony1-general] Long running TX causing out of memory errors...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Darcy Buskermolen wrote: >On Monday 12 September 2005 00:16, Philip Warner wrote: > > >>Philip Warner wrote: >> >> >>>2005-09-12 12:22:14 EST FATAL dstring_addchar: realloc() - Cannot >>>allocate memory2005-09-12 12:22:14 EST DEBUG1 slon: shutdown requested >>> >>> >>Further to this; the virtual mem size of the process is about half a gig >>when it dies...so it looks like some kind of leak. >> >> > >is there any possibility you could run this under valgrind and report what you >see? > > I am beginning to think this relates to the size of the update. I now have a situation where it crashes almost immediately on startup every time. I have tried setting the group size to 1, but it still dies. Anyone have some suggestions?
- Previous message: [Slony1-general] "realloc() - Cannot allocate memory" errors
- Next message: [Slony1-general] Long running TX causing out of memory errors...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list