Thu Sep 15 03:53:29 PDT 2005
- Previous message: [Slony1-general] Long running TX causing out of memory errors...
- Next message: [Slony1-general] Long running TX causing out of memory errors...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
--On Thursday, September 15, 2005 11:41 AM +1000 Philip Warner <pjw at rhyme.com.au> wrote: > It's the slon worker process that dies by exhausting its memory. It > seems to want to read the entire xid's worth of log entries into memory > while applying them in background, and since reading is a lot faster What happens to the data on the origin when this happens? Is there any corruption? How would we recover from this? Do we have to rebuild the nodes or just restart the slon?
- Previous message: [Slony1-general] Long running TX causing out of 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