| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
| Cc: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: per backend I/O statistics[ |
| Date: | 2024-11-25 07:18:54 |
| Message-ID: | Z0Qk3nZcaVpbtCKU@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 25, 2024 at 07:12:56AM +0000, Bertrand Drouvot wrote:
> Not sure here, could custom stats start incrementing before the database system
> is ready to accept connections?
In theory, that could be possible. Like pg_stat_io currently, I am
ready to assume that it likely won't matter much.
> The only cons that I can see is that we will not be able to merge the flush cb
> but I don't think that's a blocker (the flush are done in shared memory so the
> impact on performance should not be that much of an issue).
The backend and I/O stats could begin diverging as a result of a new
implementation detail, and the performance of the flushes don't worry
me knowing at which frequency they happen on a live system.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2024-11-25 07:21:11 | Re: POC, WIP: OR-clause support for indexes |
| Previous Message | Bertrand Drouvot | 2024-11-25 07:12:56 | Re: per backend I/O statistics |