| 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: | 2025-01-14 04:56:13 |
| Message-ID: | Z4XubXZ2T0RqDfcl@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 10, 2025 at 01:56:01PM +0000, Bertrand Drouvot wrote:
> So now, I think that it is not a good idea for the per backend stats to
> behave differently than the other stats kinds. I think we should get rid of
> the "snapshot" for all of them or for none of them. Reading the above comments,
> it looks like it has already been discussed and that the outcome is to keep
> it for all of them.
Thanks a lot for diving into these details! I did not recall that
there was a strict argument for the current behavior, even if I was
pretty sure that introducing an exception for the backend stats was
not quite right compared to the other stats kinds. The consistency
line prevails here, then.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-01-14 04:57:07 | Re: Conflict Detection and Resolution |
| Previous Message | Amit Kapila | 2025-01-14 04:47:52 | Re: Skip collecting decoded changes of already-aborted transactions |