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?

Commencez par asyncpg/protocol/codecs/array.pyx, en particulier par init_array_codecs et les lignes associées autour de 861-875. Examinez comment _oid et _text sont initialisés, puis évaluez les types de tableaux intégrés listés et déterminez si leur inclusion permet d’éviter les requêtes d’introspection sans les compromis soulevés dans l’issue. Le travail est terminé lorsqu’une décision claire et une modification appropriée ou une justification documentée sont disponibles.