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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
