Re: Add per-backend AIO statistics

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Add per-backend AIO statistics
Date: 2026-07-08 06:52:20
Message-ID: ak3zpA2HHh5CxQK8@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 07, 2026 at 11:02:03AM +0000, Bertrand Drouvot wrote:
> 1/ pg_aios that lists all AIO handles that are currently in use. That shows
> what's happening right now, but not what has happened.
>
> 2/ pg_stat_get_backend_io() that shows how much IO was done, but not how it
> was done. There's no way to see whether IOs ran synchronously or
> asynchronously, whether a backend was stalling on handle exhaustion, or how
> completions are distributed across backends.

While the information may be useful, one thing that sounds very
important to me is how this impacts workloads by default.

Andres is usually able to catch bottlenecks that everybody else is
unable to see, so perhaps checking with him the location of these
extra function calls would be a good first step. Your proposal goes
down to pgaio_io_stage(), pgaio_io_process_completion() and
pgaio_submit_staged() to track these counter increments.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message solai v 2026-07-08 06:52:28 Re: Proposal: INSERT ... BY NAME
Previous Message wenhui qiu 2026-07-08 06:37:36 Re: WAL compression setting after PostgreSQL LZ4 default change