Re: proposal: enhancing slow query log, and autoexplain log about waiting on lock before query exec time

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: enhancing slow query log, and autoexplain log about waiting on lock before query exec time
Date: 2016-02-14 17:24:39
Message-ID: CAFj8pRDpSgjVyRnvPBtHQDwcejyjr9pguJvhWxa_Y3oaUbAE7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2016-02-14 17:46 GMT+01:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> > We have a patch, that inject logs about the time waiting on locks before
> > query execution. This feature helps us lot of, and I hope, it can be
> > generally useful.
>
> Doesn't log_lock_waits cover that territory already?
>

It does. But It creates different log entry - and can be hard to join slow
query with log entry sometimes lot of lines before. This proposal is about
taking important information comfortably - and log parsing and processing
is simpler.

Regards

Pavel

> regards, tom lane
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-02-14 18:33:03 Re: [COMMITTERS] pgsql: Introduce group locking to prevent parallel processes from deadl
Previous Message Tom Lane 2016-02-14 16:51:14 Re: Bool btree_gin index not chosen on equality contraint, but on greater/lower?