Re: TODO request: log_long_transaction
От | Jim Nasby |
---|---|
Тема | Re: TODO request: log_long_transaction |
Дата | |
Msg-id | 54665FDE.8060703@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: TODO request: log_long_transaction (Michael Banck <michael.banck@credativ.de>) |
Список | 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@agliodbs.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 runsfor too long. -- Jim Nasby, Data Architect, Blue Treble Consulting Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-hackers по дате отправления: