Avoiding introspection queries for built-in array types

还没有人认领这个 Issue。

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 的初始化方式，然后评估列出的内置数组类型，以及包含这些类型是否能避免 introspection 查询，同时不会带来 issue 中提出的权衡。完成的标准是作出明确的决定，并进行适当的更改或记录相应的理由。

由索引模型根据 Issue 内容生成。