| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, 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 20:52:53 |
| Message-ID: | 14144.1260910373@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Dec 15, 2009 at 3:45 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Put a ulimit command in the server start script? Depending on the
>> details of the start script you might need to put it in the postgres
>> user's .profile instead, but it's certainly doable.
> This may be a stupid question, but when you hit the limit, will it
> result in an ERROR or a PANIC?
Should be an ERROR ... if it isn't, that's probably a bug. The design
intention is that malloc failure is just an ERROR.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Travers | 2009-12-16 00:16:26 | BUG #5246: Misleading/inconsistent SQLSTATE behavior |
| Previous Message | Robert Haas | 2009-12-15 20:46:22 | Re: statement_timeout is not cancelling query |