| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, Thom Brown <thom(at)linux(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TODO request: log_long_transaction |
| Date: | 2014-11-14 20:02:38 |
| Message-ID: | 54665FDE.8060703@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/7/14, 1:19 PM, Michael Banck wrote:
> Am Montag, den 27.10.2014, 19:29 +0000 schrieb Thom Brown:
>> >On 27 October 2014 19:21, Josh Berkus<josh(at)agliodbs(dot)com> wrote:
>>> > >I just realized that there is one thing we can't log currently:
>>> > >transactions which last more than #ms. This is valuable diagnostic
>>> > >information when looking for issues like causes of bloat and deadlocks.
>>> > >
>>> > >I'd like it to be on the TODO list because it seems like part of a good
>>> > >GSOC project or first-time contribution.
>> >
>> >
>> >So effectively, log_min_duration_transaction? Sounds useful.
FWIW, I've also wanted the equivalent of statement_timeout for transactions; the ability to abort a transaction if it runs for too long.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Harris | 2014-11-14 20:27:01 | Re: EXPLAIN ANALYZE output weird for Top-N Sort |
| Previous Message | Szymon Guz | 2014-11-14 20:00:11 | Re: printing table in asciidoc with psql |