Skip site navigation (1) Skip section navigation (2)

Re: 8.2.4 signal 11 with large transaction

From: "Chris Hoover" <revoohc(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 01:36:34
Message-ID: 1d219a6f0707211836g7a152e3fm69a645ee022617fe@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster



I know my 2 cents are not worth that much, but as a DBA, I would really like
for you to print at least some of the string causing the abend.  This would
greatly assist in the tracing of the offending query.

Chris

In response to

pgsql-hackers by date

Next:From: Sibte AbbasDate: 2007-07-22 04:05:29
Subject: Re: 8.2.4 signal 11 with large transaction
Previous:From: Andrew DunstanDate: 2007-07-21 21:36:44
Subject: Re: Query plan and execution time of a query

pgsql-general by date

Next:From: TejuDate: 2007-07-22 02:53:02
Subject: spool function in nbtree index
Previous:From: Stefan BerglundDate: 2007-07-21 23:54:28
Subject: Re: PGInstaller Project

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group