From: | Jon Jensen <jon(at)endpoint(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Can't find thread on Linux memory overcommit |
Date: | 2003-08-21 14:03:27 |
Message-ID: | Pine.LNX.4.50.0308211358330.7041-100000@louche.swelter.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Thu, 21 Aug 2003, Andrew Dunstan wrote:
> Linux kernel version 2.4.* has poor default memory overcommit behavior,
> which can result in the postmaster being killed by the kernel due to
> memory demands by another process if the system runs out of memory. To
> avoid this situation, run postgres on a machine where you can be sure
> that other processes will not run the machine out of memory.
I would also note that the OOM killer logs its evil deeds:
printk(KERN_ERR "Out of Memory: Killed process %d (%s).\n", p->pid, p->comm);
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.
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2003-08-21 16:16:29 | Re: Can't find thread on Linux memory overcommit |
Previous Message | Andrew Dunstan | 2003-08-21 13:19:24 | Re: Can't find thread on Linux memory overcommit |
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-08-21 14:18:28 | Re: [pgsql-advocacy] Need concrete "Why Postgres not MySQL" |
Previous Message | Greg Stark | 2003-08-21 13:21:01 | Re: [pgsql-advocacy] Need concrete "Why Postgres not MySQL" |