Re: [BUG]: the walsender does not update its IO statistics until it exits

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [BUG]: the walsender does not update its IO statistics until it exits
Date: 2025-02-27 10:06:15
Message-ID: kcgnbp6twtl6rj6lqy5whqv6kua2u5l74o2gy5serop7tnhlp7@omvay3wvmm5v
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-02-27 12:09:46 +0900, Michael Paquier wrote:
> I suspect that there would be cases where a single stats kind should be able
> to handle both transactional and non-transactional flush cases. Splitting
> that across two stats kinds would lead to a lot of duplication.

Agreed. Table stats will be the prime case where that's important.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2025-02-27 10:09:40 Re: Some read stream improvements
Previous Message Rushabh Lathia 2025-02-27 09:55:51 Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints