On Tue, Sep 6, 2011 at 4:52 PM, Marti Raudsepp <ma...@juffo.org> wrote: > This patch adds the backend's current running query to the "backend > crash" message. > > The crashing query is often a good starting point in debugging the > cause, and much more easily accessible than core dumps. > > Example output: > LOG: server process (PID 31451) was terminated by signal 9: Killed > DETAIL: Running query: DO LANGUAGE plpythonu 'import > os;os.kill(os.getpid(),9)' > > The message "Running query" might not be entirely true, as it might be > e.g. a vacuum activity string too. But it sounds better than "Activity > string" or anything else I could come up with. > > Also refactored pgstat_get_backend_current_activity() such that it > always returns consistent results. (Previously it returned a pointer to > shared memory that could theoretically change and was vulnerable to > races) The function can also deal with shared memory corruption (if > isCrashed is true), so that corruption doesn't cause a postmaster crash > or hang.
I haven't looked at the patch, but boy would this save me a lot of support headaches if we can make it work. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
