On 11/7/14, 1:19 PM, Michael Banck wrote:
Am Montag, den 27.10.2014, 19:29 + schrieb Thom Brown:
>On 27 October 2014 19:21, Josh Berkus wrote:
> >I just realized that there is one thing we can't log currently:
> >transactions which last more than #ms. This is valuable diagnostic
> >inform
Robert Haas wrote:
>> 3. Should long transactions which are rolled back be logged as well?
>
> Yes.
+1
>> 4. We log the statement when exceeding log_min_duration_statement, but
>> for transactions, that does not make a lot of sense, or should the last
>> statement be logged? I don't think that
You should add this patch here, so it doesn't get forgotten:
https://commitfest.postgresql.org/action/commitfest_view/open
On Fri, Nov 7, 2014 at 2:19 PM, Michael Banck wrote:
> 1. Should this log when the duration is exceeded (like log_lock_waits),
> or on commit? I guess the latter, cause log_
Hi,
Am Montag, den 27.10.2014, 19:29 + schrieb Thom Brown:
> On 27 October 2014 19:21, Josh Berkus 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 ca
On 27 October 2014 19:21, Josh Berkus wrote:
> Hackers,
>
> 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
Hackers,
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
