|From:||Tory M Blue <tmblue(at)gmail(dot)com>|
|Views:||Raw Message | Whole Thread | Download mbox|
Is there anyone that could help me understand why all of a sudden with
no noticeable change in data, no change in hardware, no change in OS,
I'm seeing postmaster getting killed by oom_killer?
The dmesg shows that swap has not been touched free and total are the
same, so this system is not running out of total memory per say.
I keep thinking it's something to do with lowmem vs highmem 32bit vs
64 bit, but again no changes and I'm getting hit nightly on 2
different servers (running slon, so switched over and same thing, even
disabled memory over commit and still got nailed.
Is there anyone familiar with this or could take a look at the dmesg
output (off list) and decipher it for me?
this is a Fedora 12 system, 188.8.131.52-170. I've been reading and
appears this is yet another fedora bug, but so far I have not found
any concrete evidence on how to fix it.
32gig memory, 8 proc
postgres 8.4.4, slony 1.20
5 gigs of swap (never hit it!)
|Next Message||yoshi watanabe||2011-04-21 12:37:11||Re: oom_killer|
|Previous Message||Laurent Laborde||2011-04-21 08:02:07||Re: postgresql random io test with 2 SSD Kingston V+100 500GB in (software) Raid1|