Guys,
> So there's no need to wonder whether that's a source of trouble for your
> PostgreSQL processes or not; just check the logs. I've had the OOM killer
> go after large Perl processes and X, but never (yet) PostgreSQL, I'm happy
> to say.
Well, sadly, the reason I posted is that I (apparently) had a client's
database fatally corrupted by this problem.
Downloading Alan Cox's patch now ....
--
Josh Berkus
Aglio Database Solutions
San Francisco
