Avoiding introspection queries for built-in array types

Hi, and thanks for all the work on asyncpg! 👋

I’ve noticed that fresh connections usually emit introspection queries even for statements involving simple arrays of integers.

Looking at the code in init_array_codecs, asyncpg seems to initialize only the core codecs for _oid and _text (as mentioned in the comment, “to make type introspection query work”).

https://github.com/MagicStack/asyncpg/blob/5b14653e0b447d956aa01ec658562138e19f0293/asyncpg/protocol/codecs/array.pyx#L861-L875

I was wondering: was there a particular reason that asyncpg doesn’t include more built-in types there? From my perspective, types like _int2, _int4, _int8, _float4, _float8, _bool, and _char are very commonly used in queries. Including them might avoid a lot of introspection queries on new connections.

Is this something that could be considered, or are there trade-offs I might be missing?

asyncpg/protocol/codecs/array.pyx から始め、特に init_array_codecs と 861-875 前後の関連する行を確認してください。_oid と _text がどのように初期化されるかを確認し、次に列挙されている組み込み配列型を評価して、それらを含めることで、issue で提起されたトレードオフなしにイントロスペクションクエリを回避できるかどうかを検討してください。明確な判断と、適切な変更または文書化された根拠があれば完了です。