Re: [PATCH] Change wait_time column of pg_stat_lock to double precision

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: kawatatatsuya0913(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
Date: 2026-06-15 13:54:54
Message-ID: ajAELqNEVYQ89nv5@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-06-15 14:17:18 Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope
Previous Message Amit Kapila 2026-06-15 13:53:00 Re: Report bytes and transactions actually sent downtream