From: | Scott Mead <scottm(at)openscg(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | IDLE in transaction introspection |
Date: | 2011-10-31 21:37:33 |
Message-ID: | CAKq0gvK8PzMWPv19_o7CGg8ZQ0G+UuAWor5RrAg0SOmWTqqLwg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey all,
So, I'm dealing with a a big ol' java app that has multiple roads on the
way to <IDLE> in transaction. We can reproduce the problem in a test
environment, but the lead dev always asks "can you just tell me the last
query that it ran?"
So I wrote the attached patch, it just turns <IDLE> in transaction into:
"<IDLE> in transaction\n: Previous: <last query executed>". After seeing
how quickly our dev's fixed the issue once they saw prepared statement XYZ,
I'm thinking that I'd like to be able to have this in prod, and... maybe
(with the frequency of IIT questions posted here) someone else would find
this useful.
Just wondering what ya'll thought. Any feedback (including a more
efficient approach) is welcome. (Patch against release 9.1.1 tarball).
Thanks!
--
Scott Mead
OpenSCG
Attachment | Content-Type | Size |
---|---|---|
idleInTrans.911.patch | application/octet-stream | 2.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2011-10-31 21:42:47 | Re: Multiple queries in transit |
Previous Message | Tom Lane | 2011-10-31 20:43:18 | Re: Optimizing GetRunningTransactionLocks() |