| 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: 8.2.4 signal 11 with large transaction |
| Date: | 2007-07-22 04:05:29 |
| Message-ID: | bd6a35510707212105w4e2b3761l9c4564b1f5a3db6a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 7/20/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I guess what we need to do is hack the emergency-recovery path for
> error-during-error-processing such that it will prevent trying to print
> a very long debug_query_string. Maybe we should just not try to print
> the command at all in this case, or maybe there's some intermediate
> possibility like only printing the first 1K or so. Thoughts?
>
> regards, tom lane
>
I think printing the first 1K would make more sense.
If I understand you correctly, the code path which you are referring
to is the send_message_to_server_log() function in elog.c?
thanks,
--
Sibte Abbas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shreya Bhargava | 2007-07-22 04:33:23 | Debugging postgresql source on gdb |
| Previous Message | Michael Fuhr | 2007-07-22 03:47:06 | Re: posgres tunning |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2007-07-22 05:58:25 | Re: 8.2 is 30% better in pgbench than 8.3 |
| Previous Message | Chris Hoover | 2007-07-22 01:36:34 | Re: 8.2.4 signal 11 with large transaction |