| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: kill -KILL: What happens? |
| Date: | 2011-01-13 23:29:13 |
| Message-ID: | 1294961353.1528.18.camel@jdavis-ux.asterdata.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2011-01-13 at 11:14 -0800, David Fetter wrote:
> I get that we can't prevent all pilot error, but I was hoping we could
> bullet-proof this a little more, especially in light of a certain
> extremely popular server OS's OOM killer's default behavior.
That's a good point. I'm not sure how much action can reasonably be
taken, however.
> Yes, I get that that behavior is crazy, and stupid, and that people
> should shut it off, but it *is* our problem if we let the postmaster
> start (or continue) when it's set that way.
As an aside, linux has actually changed the heuristic:
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2011-01-13 23:32:14 | Re: kill -KILL: What happens? |
| Previous Message | Kevin Grittner | 2011-01-13 23:24:31 | Re: auto-sizing wal_buffers |