Re: [PATCH] Change wait_time column of pg_stat_lock to double precision - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
Date
Msg-id ajAELqNEVYQ89nv5@bdtpg
Whole thread
In response to Re: [PATCH] Change wait_time column of pg_stat_lock to double precision  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
List pgsql-hackers
Hi,

On Mon, Jun 15, 2026 at 04:39:22PM +0900, Kyotaro Horiguchi wrote:
> Hello.
> 
> At Mon, 15 Jun 2026 15:54:24 +0900, Tatsuya Kawata <kawatatatsuya0913@gmail.com> wrote in 
> > While looking at the lock-related code, I noticed that pg_stat_lock
> > is the only statistics view whose timing column (wait_time) uses
> > bigint.  Every other statistics view uses double precision for
> > measured-time columns.  I do not see a reason for pg_stat_lock to
> > differ.
> 
> It seems to me that this was intentional. As described in the
> documentation, since wait_time is only accumulated for waits longer
> than deadlock_timeout, sub-millisecond precision was probably not
> considered particularly useful.

Yeah that was intentional (and for the reason you described above).

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Report bytes and transactions actually sent downtream
Next
From: Bertrand Drouvot
Date:
Subject: Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope