Re: Add AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl

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 AioUringCompletion in wait_event_names.txt and a safeguard in generate-wait_event_types.pl
Date: 2025-05-29 04:31:12
Message-ID: aDfjEBRnu5yjH5SL@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, May 27, 2025 at 08:30:56AM +0900, Michael Paquier wrote:
> +AioUringCompletion "Waiting for another process to complete IO via io_uring."
>
> "completion_lock" is described with similar words around the top of
> method_io_uring.c. In more exact words, we are waiting for a backend
> to process IO completions with io_method=io_uring. So perhaps:
> "Waiting for another process to process IO completions with io_uring"

Hearing nothing, I've applied this one reusing the exact wording
suggested by Bertrand which is the most consistent choice with the
other wait events related to the same area of the code.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2025-05-29 04:35:37 Re: Foreign key validation failure in 18beta1
Previous Message Fujii Masao 2025-05-29 04:28:45 Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE