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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: Tatsuya Kawata <kawatatatsuya0913(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(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-29 04:52:54
Message-ID: akH6Jv6xoyRQeYWZ@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 29, 2026 at 04:27:55AM +0000, Bertrand Drouvot wrote:
> postgres=# select read_time from pg_stat_io where read_time > 0;
> read_time
> ---------------------
> 2.2640000000000002
> 0.08700000000000001
>
> Maybe it should be changed to?

pg_stat_io with track_io_timing enabled shows the same thing. FWIW,
that does not bother me much. It's just more important to me to apply
the same formulas across the board.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2026-06-29 04:56:11 Re: [PATCH] Change wait_time column of pg_stat_lock to double precision
Previous Message Bertrand Drouvot 2026-06-29 04:52:32 Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope