On 12-06-07 10:22 AM, Zac Bentley wrote: > 1. 2.0.7, correct. > 2. I don't know for certain. I'm running another initial subscribe right now > but it will take some time before it gets to the critical point. I would > assume that the Slons are the ones eating memory, since I know from > experience that the OOM killer will kill Postgres quite readily. Something > that the OOM killer can't touch is leading to the system running out of > memory, so I'd assume the Slons.
Keep an eye on it. I can't think of a reason why the slon memory footprint should grow like that. > 3. No, it doesn't. It gets part of the way through subscription of a large > table and then the lots start showing watchdog-restarts, 4 or 5 times, and > then the system kernel panics. What is the reason/message given for the slon workers being killed? Is the OOM killer, killing them? Off the top of my head I can't think of a reason why the OOM killer couldn't kill a slon. (should the OOM killer be killing slons is a different question). > 4. If I restart them after the crash without touching anything, the > subscription process starts again from the very beginning. > > Zac Bentley > Systems Administrator > Corporate Reimbursement Services, Inc. > www.crsinc.com > 617-467-1949 > > This email message contains information that Corporate Reimbursement > Services, Inc. considers confidential and/or proprietary, or may later > designate as confidential and proprietary. It is intended only for use of the > individual or entity named above and should not be forwarded to any other > persons or entities without the express consent of Corporate Reimbursement > Services, Inc., nor should it be used for any purpose other than in the > course of any potential or actual business relationship with Corporate > Reimbursement Services, Inc. If the reader of this message is not the > intended recipient, or the employee or agent responsible to deliver it to the > intended recipient, you are hereby notified that any dissemination, > distribution, or copying of this communication is strictly prohibited. If you > have received this communication in error, please notify sender immediately > and destroy the original message. > > Internal Revenue Service regulations require that certain types of written > advice include a disclaimer. To the extent the preceding message contains > advice relating to a Federal tax issue, unless expressly stated otherwise the > advice is not intended or written to be used, and it cannot be used by the > recipient or any other taxpayer, for the purpose of avoiding Federal tax > penalties, and was not written to support the promotion or marketing of any > transaction or matter discussed herein. _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
