Re: [PATCH] Log crashed backend's query (activity string) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Log crashed backend's query (activity string)
Date
Msg-id 1724.1315426523@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Log crashed backend's query (activity string)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Log crashed backend's query (activity string)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Sep 7, 2011 at 3:42 PM, Alvaro Herrera
> <alvherre@commandprompt.com> wrote:
>> A mishandled encoding conversion could be problematic, so that needs to
>> be carefully considered (perhaps just shut off unconditionally).

> It's not really a problem for the postmaster if something just plain
> old fails.  Where we get into trouble is if it manages to (a) crash,
> (b) take an excessive amount of time to complete, or (c) screw up the
> postmaster state in some way we can't recover from.  But if any of
> those are an issue then, yeah, just shut it off.

Keep in mind that in the postmaster, elog(ERROR) *is* a crash.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] Log crashed backend's query (activity string)
Next
From: daveg
Date:
Subject: Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held