| From: | "Sibte Abbas" <sibtay(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bill Moran" <wmoran(at)collaborativefusion(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] 8.2.4 signal 11 with large transaction |
| Date: | 2007-07-23 20:38:45 |
| Message-ID: | bd6a35510707231338n32d6c05fxd705d5f50ae3cba9@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 7/23/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> No, the place that has to change is where errstart() detects that we're
> recursing. We could possibly have it first try to make a shorter string
> and only give up entirely if recursion happens again, but given that
> this is such a corner case I don't think it's worth the complexity and
> risk of further bugs. I've made it just drop the statement at the same
> time that it decides to give up on printing other context (which can
> also be a source of out-of-memory problems btw).
> http://archives.postgresql.org/pgsql-committers/2007-07/msg00215.php
>
Makes sense.
regards,
--
Sibte Abbas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-07-23 21:09:52 | Re: Delete/update with limit |
| Previous Message | Ron Johnson | 2007-07-23 20:26:27 | Re: Delete/update with limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-07-23 21:02:31 | Reviewing new index types (was Re: [PATCHES] Updated bitmap indexpatch) |
| Previous Message | Tom Lane | 2007-07-23 20:03:14 | Re: COPYable logs |