[Feature Request]Adding compatibility support for KingbaseES

Open

#1,318 opened on Apr 27, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: postgresql, python
Domain: databases

Research direction

Start by reviewing asyncpg/protocol/ and the existing Authentication and Type Introspection SQL paths to identify the PostgreSQL assumptions relevant to KingbaseES. Compare those paths with the reported pg_catalog differences and decide whether server-version detection or an explicit connection flag is appropriate. Done means basic connections work, variant-specific integration tests pass, and the full asyncpg test suite remains stable against KingbaseES.

Written by the indexing model from the issue text.

Description

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!

Dominant language: Python
Stars: 8.1k
Forks: 469
Avg merge: 2d 20h
Merged PRs (30d): 9

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

create_predictable_zip member order differs on Windows for directory input Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 90/100

learningequality/ricecooker#747 · Opened Sep 23, 2026
[Anon] Mechanicum: skitarii as mechanicum allies rule Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

BSData/horus-heresy-3rd-edition#3171 · Opened Sep 23, 2026
CHANGELOG.md entries are too long to maintain, and their length is what makes every PR conflict expensive Open

enhancement

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

lanl/PyBNF#809 · Opened Sep 23, 2026
[Bug]: PrevNextNodePostprocessor loses retrieved scores when neighbor windows overlap Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

run-llama/llama_index#23199 · Opened Sep 23, 2026
Cannot export point cloud without radius attribute Open

Difficulty 2/5 1-3 hours Newbie friendliness 84/100

KhronosGroup/glTF-Blender-IO#2769 · Opened Sep 23, 2026

More Python issues