| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Stephen Frost <sfrost(at)snowman(dot)net>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL 8.0.6 crash |
| Date: | 2006-02-10 17:21:25 |
| Message-ID: | 21288.1139592085@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Disclaimer: The Linux OOM killer has never killed the wrong process for
> me, so I don't have any bad experiences with overcommit.
You haven't tried real hard. What I've seen recently when I do something
that makes a PG backend go overboard is that the kernel zaps both the
misbehaving backend and the bgwriter process. No idea what it's got
against the bgwriter, but the behavior's been pretty consistent under
recent Fedora 4 kernels ...
(This is on a development machine, not a server, so I'm not particularly
worried by leaving the default overcommit policy in place. I wouldn't
do that on a server --- but it's not worth my time to change it on a
devel machine.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2006-02-10 17:46:27 | Re: Scrollable cursors and Sort performance |
| Previous Message | Tom Lane | 2006-02-10 17:16:25 | Re: Backslashes in string literals |