[Feature Request]Adding compatibility support for KingbaseES

还没有人认领这个 Issue。

Hi asyncpg maintainers,

I am writing to propose adding support for KingbaseES, a widely used database in China that is highly compatible with the PostgreSQL wire protocol. I plan to contribute and maintain this adaptation over the next 2 months.

To ensure the performance and stability of asyncpg remain unaffected, I will follow these principles:
1.Non-Invasive Implementation: I will not modify the Cython-based protocol parser (asyncpg/protocol/). The changes will be isolated to Authentication tweaks and Type Introspection SQL adjustments (handling minor pg_catalog differences).
2.Strict Testing: I will run the full asyncpg test suite against KingbaseES and add dedicated integration tests for any variant-specific edge cases.
3.Maintenance Commitment: I fully understand the burden of supporting variants. I commit to taking long-term ownership of Kingbase-related issues to keep the driver up-to-date.

I have already verified basic connections locally. Would the community be open to accepting a Pull Request for this? Also, do you prefer handling such variants via automatic detection (server version) or explicit connection flags?
Thank you for your incredible work on this high-performance driver!

首先检查 asyncpg/protocol/ 以及现有的 Authentication 和 Type Introspection SQL 路径，以识别与 KingbaseES 相关的 PostgreSQL 假设。将这些路径与报告中的 pg_catalog 差异进行比较，并决定采用服务器版本检测还是显式连接标志更为合适。当基本连接正常工作、特定变体的集成测试通过，并且完整的 asyncpg 测试套件在 KingbaseES 上仍保持稳定时，即视为完成。

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