On Mon, 2008-02-04 at 15:31 -0500, Tom Lane wrote: > I cannot see any way of restricting global memory > consumption that won't hurt performance and flexibility.
We've discussed particular ways of doing this previously and not got very far, its true. I think we need to separate problem identification from problem resolution, so we can get past the first stage and look for solutions. This is my longest running outstanding problem with managing Postgres on operational systems. Sure, OOM killer sucks. So there's two problems, not one. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
