Minor adjustment to pg_aios output naming
torikoshia <torikoshia@oss.nttdata.com>
From: torikoshia <torikoshia@oss.nttdata.com>
To: Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2025-05-21T02:14:11Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Adjust operation names of pg_aios to match the documentation
- 3d0c3a418fc2 18.0 landed
Attachments
- v1-0001-Adjust-pg_aios-operation-names-to-match-documenta.patch (text/x-diff) patch v1-0001
Hi, I've noticed a minor inconsistency in the output of pg_aios. According to the documentation, the values for 'operation' are described as: <literal>readv</literal>, a vectored read ... <literal>writev</literal>, a vectored write However, in actual output, they appear as read and write -- without the trailing v: =# select operation from pg_aios; .. operation | read While this discrepancy is unlikely to cause any real issues, it would be better to keep the naming consistent. I was a bit unsure which form to align to. There are currently no other types of read/write operations in pg_aios, so the shorter form might have been sufficient. However, using the 'v'-suffixed names makes the vectored nature of these operations explicit and future-proofs the naming in case other variants are introduced later. What do you think? Best regards, -- Regards, -- Atsushi Torikoshi Seconded from NTT DATA GROUP CORPORATION to SRA OSS K.K.