Skip to main content
  1. Posts/

A DBA's Perspective on the 0526 Approved Database List

liuzhilong62
Author
liuzhilong62
PostgreSQL DBA. Writing about database internals, production cases, and source code analysis.

AI rate 5%

TL;DR
#

On May 26, the Xinchuang Database List 2026 No. 2 was released, with 23 products passing (8 centralized + 15 distributed) — the most ever. Most notably: Ping An, UnionPay, China Mobile, and China Telecom — four major buyers — had their self-incubated databases debut on the list. The Xinchuang logic has changed — buyers are no longer just buyers.

The Latest List
#

Historical batch statistics for the Xinchuang database list. Data source: China Information Security Evaluation Center (itsec.gov.cn), 8 batches total, 4 containing databases.

By Batch

BatchDateDatabase ProductsAchieved Level II
2023#12023-12-2611 (centralized)None
2024#22024-09-3017 (6 centralized + 11 distributed)GaussDB
2025#22025-08-223 (centralized)None
2026#22026-05-2623 (8 centralized + 15 distributed)Dameng/Yashan/GaussDB/GoldenDB

By Appearances (≥2 times)

VendorCount
Dameng3
GBASE3
Alibaba Cloud3
HighGo2
Tencent Cloud2
East Golden2
Vastdata2
Huawei Cloud2
ZTE (GoldenDB)2
OceanBase2
Kingbase2
Shentong2
Xugu2
Yashan2
Only 1 timePingCAP/Wanli/Uxin/Ping An/China Mobile/UnionPay/Telecom Cloud/Timecho/Transwarp/DolphinDB/Z-Range/CM Suzhou

By Category: Big Tech / Unicorn / Major Buyer

CategoryVendors
Big TechHuawei Cloud (GaussDB/TaurusDB/DWS), Alibaba Cloud (PolarDB/AnalyticDB), Tencent Cloud (TDSQL), ZTE (GoldenDB), OceanBase (Ant Group)
UnicornsPingCAP (TiDB), Yashan (SICS), Transwarp (ArgoDB), Timecho (TimechoDB), DolphinDB
Major BuyersPing An Tech (RASESQL), China UnionPay (UPDRDB), China Mobile (Panwei + He3DB), China Telecom Cloud (TeleDB)
Traditional XinchuangDameng, Kingbase, GBASE, Shentong, HighGo, Xugu, Vastdata, East Golden, Wanli, Uxin

The Floodgates Open
#

When this list came out, my reaction was four words: the floodgates opened. 23 products — the most ever. A few highlights:

Ping An RASESQL. The most unexpected. Ping An Group’s fintech capabilities have always been strong, but there was almost no public information about them building a database. Seeing “RASESQL” on the list stunned me for several seconds. A financial buyer of Ping An’s scale — once their self-developed database passes national testing, their internal Xinchuang replacement roadmap gains one more path.

UnionPay UPDRDB. Equally mysterious. I had no idea UnionPay was building a distributed database before this. UnionPay’s transaction volume speaks for itself — a distributed database that can handle their own business won’t be technically weak.

Alibaba Cloud PolarDB for MySQL. The MySQL-compatible edition of PolarDB not passing had been something many people remembered. Now, all three of PolarDB’s main lines — PG edition, distributed edition, MySQL edition — have passed. Add AnalyticDB, and Alibaba Cloud’s database family is basically complete.

China Mobile Panwei + China Telecom TeleDB. China Mobile already had He3DB (CM Suzhou) pass national testing last year; this year Panwei is their second product. China Telecom TeleDB debuts. Both telecom operators now have their own incubated Xinchuang databases, which should significantly reduce their respective Xinchuang replacement pressure. Interestingly, China Unicom has been silent — their Xinchuang strategy is clearly different from Mobile and Telecom.

Transwarp ArgoDB. Transwarp started in the big data/Hadoop ecosystem and now their distributed database has passed national testing. Once crowned “China’s First Domestic Big Data Infrastructure Software Stock” with a market cap exceeding 30 billion, their path from data lake to Xinchuang database has been validated.

Impact
#

The most important signal from this floodgate opening: buyers can self-develop databases.

What are the implications?

  • Major buyers who succeed at self-development don’t have to be lambs to the slaughter.
  • Those major buyers who haven’t built one yet may restart their self-development efforts.
  • The market share that big tech and unicorns could compete for in the domestic database market just shrank.

Financial industry players UnionPay and Ping An, telecom players China Mobile and China Telecom — all passed national testing, effectively earning a “R&D Success” gold badge. Internally, each organization must be celebrating. For external vendors, what they’ve lost isn’t just major clients — more precisely, they’ve lost absolute bargaining power.

“I know you’re in a tough spot, and I know you can’t afford not to buy, so I’ll swap the butcher’s knife for a dragon-slaying blade and slaughter you to death” — for buyers who successfully incubated their own databases, this kind of predicament has been substantially eased. That’s significant.

As for where Xinchuang policy goes next, nobody can say. Based on previous lists, things should be getting stricter (last time only 3 databases passed), but this time they unexpectedly opened the floodgates. A sharp contraction next round isn’t impossible. Not just China Unicom — insurance industry players like CPIC and PICC, and even capable financial institutions, could consider jumping in to hand-roll their own database.

Bittersweet Reflections
#

Since our kernel team sits right behind me, I have some understanding of the Xinchuang R&D process. After consecutive failed submissions, the entire team’s morale was extremely low. I believe we weren’t the only ones — many teams whose submissions failed felt the same. For industries like finance and telecom, there’s a Xinchuang mandate, but if your self-developed product doesn’t pass approval, there’s no choice at the corporate strategy level, and at the team level, there’s no reason for existence. That’s why “passing national testing” carries such weight and influence. Thankfully they passed — heartfelt congratulations to them! RaseSQL No.1!

At the same time, it’s clear that Xinchuang results and direction are unstable, volatile, and impactful. It determines some companies’ strategies and many people’s fates. I myself am even a piece on this wheel of fortune.

Beyond those on the list, many organizations poured enormous effort but remain off the list. Their products might be terrible, or they might be excellent. But national testing is that stark watershed — a mysterious ticket of admission. Pass or fail — in the domestic market, those are two entirely different concepts.

OK, just some thoughts — might delete later.

Reference
#

https://www.itsec.gov.cn/aqkkcp/cpgg/

Original link: https://lastdba.com/2026/05/29/xinchuang-db-2026-review/

Related

My Blog is Live

·508 words·3 mins
It’s Live! # The blog is finally live. URL: https://lastdba.com Accessible from China, mobile-friendly too. 76 articles — all PostgreSQL writing from the past few years: case studies, internals, source code analysis, paper deep reads. This is a proper launch: new framework, new domain, new theme — rebuilt from the ground up. Highlights # Clean Interface Minimalist, reader-friendly design with a useful search feature.

My 2025 Year-End Summary

·2411 words·12 mins
As a DBA # As a DBA, I strongly believe in first principles and information theory when it comes to problem analysis. A DBA needs to deeply understand the system, understand PostgreSQL, to explain anomalies from first principles. For example, in the first half of the year I spent considerable effort understanding Linux memory, exploring the essence of memory issues and their solutions. At the same time, this year I took a step forward in system operations — no longer focusing solely on technical problems and handling, but more on providing solutions. These should encompass thinking across the PostgreSQL database technology dimension, the system dimension, and the management dimension.

My 2024 Year-End Summary

·1910 words·9 mins
As a DBA # 2023 was a year of comprehensive PostgreSQL learning for me, and 2024 has been a year of comprehensive PostgreSQL operations. There’s actually a lot of material I really want to dive into but haven’t had the time. This year was mainly case analysis — I could only supplement my foundational knowledge here and there. Mid-year there was a discussion about “will DBAs be eliminated in the cloud era.” This discussion left a deep impression on me. I thought about many things afterward — why do others seem to have so few things to deal with while I, as a DBA, have so much? I even went into cloud computing groups to debate about it, and I actually gained something from it. Different perspectives lead to unexpected conclusions. The conclusion of the debate may boil down to just one thing: DBAs are providing 1510 emotional value to their leaders.