Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: kawatatatsuya0913@gmail.com, pgsql-hackers@lists.postgresql.org
Date: 2026-06-15T13:54:54Z
Lists: 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
Commits
-
Change stat_lock.wait_time to double precision
- ff6f6e0470ec 19 (unreleased) landed
- c776550e4662 master landed