| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Mark Williamson <thetazzbot(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: statement_timeout is not cancelling query |
| Date: | 2009-12-15 17:07:15 |
| Message-ID: | 407d949e0912150907j43014a90wb964d7db07a7609a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 15, 2009 at 4:16 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I didn't know that, but it I think by the time malloc returns 0
> usually other bad things are happening. I don't think that's really
> an answer.
Only if, as Craig said and you disputed, you have overcommit enabled
or lots of swap.
There is a problem though, if you have overcommit disabled you kind of
need lots of swap to avoid running out of virtual memory long before
you're actually short on physical memory. And it's true that Linux has
had trouble dealing with low memory situations in the past few years,
at least in my experience. But that's not true on all OSes and we can
hope it won't be true for Linux forever too.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-12-15 17:18:28 | Re: statement_timeout is not cancelling query |
| Previous Message | Robert Haas | 2009-12-15 16:58:49 | Re: BUG #5244: Attempting to rollback to a savepoint after receiving an error with state 55000 the process hangs |