| 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>, Marti Raudsepp <marti(at)juffo(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Log crashed backend's query (activity string) |
| Date: | 2011-09-07 20:15:23 |
| Message-ID: | 1724.1315426523@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Sep 7, 2011 at 3:42 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | daveg | 2011-09-07 20:22:00 | Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held |
| Previous Message | Robert Haas | 2011-09-07 20:02:59 | Re: [PATCH] Log crashed backend's query (activity string) |