Re: [HACKERS] pg_stat_activity.waiting_start - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pg_stat_activity.waiting_start
Date
Msg-id 17698.1482948419@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] pg_stat_activity.waiting_start  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] pg_stat_activity.waiting_start  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Jim Nasby <Jim.Nasby@bluetreble.com> writes:
> On 12/28/16 11:25 AM, Tom Lane wrote:
>> The idea of just capturing the wait start for heavyweight locks, and
>> not other lock types, still seems superior to any of the alternatives
>> that have been suggested ...

> Is some kind of alarm a viable option for the others? If setting the 
> alarm is cheap,

Setting an alarm is certain to require a gettimeofday and/or a kernel
call.  It is far from cheap.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] pg_stat_activity.waiting_start
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] merging some features from plpgsql2 project