| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | daveg <daveg(at)sonic(dot)net> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, mark(at)mark(dot)mielke(dot)cc, John Hansen <john(at)geeknet(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PG Killed by OOM Condition |
| Date: | 2005-10-25 06:15:22 |
| Message-ID: | 435DCD7A.3020008@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
daveg wrote:
> When this happens the machine runs out of memory and swap. Without the oom
> killer it simply hangs the machine which is inconvenient as it is at a remote
> location. The oom killer usually lets the machine recover and postgres restart
> without a hard reboot.
>
If vm.overcommit is set to 2, wouldn't postgres get a memory allocation
error, rather than a hung machine?
By the way, what does FreeBSD do? I've never had any memory allocation
related headaches on that platform (although I'm fairly new to FreeBSD).
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2005-10-25 08:18:14 | Surge in MySQL converters |
| Previous Message | daveg | 2005-10-25 05:52:17 | Re: PG Killed by OOM Condition |