📊 HiddenMerit Daily · Issue 56
Focus on Database Frontiers, Practical Insights for DBAs July 6, 2026 ｜ 5 Selected Global Breaking News
01｜Kingware Releases Manufacturing Scenario Database Evolution White Paper: SQL Server Replacement Enters “Deep Water”
On July 5, CETC Kingware published a technical article titled “Database Evolution in Manufacturing Scenarios: How Kingware Replaces SQL Server,” pointing out that the data surge on industrial shop floors has exceeded the processing capacity of single‑node systems. Traditional database architectures that rely on vertical scaling are facing unprecedented performance challenges. Over the next 1‑3 years, manufacturing enterprises will no longer face only the “choice of replacement,” but must answer the strategic question: “How do we build an autonomous data foundation in the context of de‑IOE?”
Three Paradigm Shifts:
- Hybrid Workloads Become the Norm: The IT architecture of modern factories is shifting from separated OLTP and OLAP to HTAP mode. The same data system must simultaneously handle tens of thousands of device instruction writes per second and minute‑level production report analysis.
- Distributed Architecture Becomes a Hard Requirement: When a single table exceeds 100 million rows with daily increments exceeding 1 million rows, the index maintenance cost of traditional single‑node databases rises exponentially.
- Autonomous Control Compliance Drives Replacement: In power, energy, and high‑end equipment manufacturing, the domestic replacement rate for core business system databases is increasing at an annual rate of over 20%.
Kingware Replacement Path: KingbaseES V9, for SQL Server migration scenarios, provides a path from smooth migration to capability enhancement through deep T‑SQL syntax compatibility (stored procedures, triggers, specific functions), KES Sharding for horizontal scaling to support PB‑level data, and KES RAC and KES ADC to achieve RPO=0/RTO<30s high availability.
- DBA Perspective: SQL Server replacement in manufacturing scenarios is entering the “deep water” zone – it’s not just about syntax conversion, but involves systematic restructuring of storage engines, transaction models, and high‑availability architectures. Kingware’s observation that “over the next 1‑3 years, manufacturing enterprises must answer this strategic question” means that Xinchuang job demand in the manufacturing sector is shifting from “edge systems” to “core production systems.” KingbaseES V9’s T‑SQL compatibility and distributed scaling capability are core considerations for DBAs evaluating SQL Server migration in manufacturing.
02｜2026 Financial Core System Domestic Database Selection Guide: 8 Products Compared Side‑by‑Side
On July 4, PingCode released the “2026 Financial Core System Domestic Database Comparison” selection guide, systematically comparing eight domestic database products: OceanBase, GoldenDB, TiDB, Vastbase, PolarDB, KingbaseES, Dameng, and TDSQL.
Core Selection Framework: Bank database domestic replacement has entered the “deep water” zone. Early projects focused on “whether it can be replaced,” but now it’s about more specific questions – can it handle core accounting? Is the transaction processing reliable? How much Oracle refactoring is required? Is disaster recovery failover stable? Will future scaling require another migration?
| Product | Core Positioning | Suitable Scale | Compatibility | Typical Scenarios |
|---|---|---|---|---|
| OceanBase | Core transaction & integrated distributed database | Medium‑large banks & core systems | Oracle, MySQL | Core accounting, payments, credit, customer info |
| GoldenDB | Financial‑grade distributed database for large banks | Large banks & high‑concurrency systems | MySQL ecosystem | Corporate/retail core, credit card core |
| TiDB | Distributed SQL & real‑time HTAP | Medium‑large banks & internet finance | MySQL | Sharding governance, transaction query, real‑time analytics |
| Vastbase | Centralised high‑availability & multi‑ecosystem migration | Small‑medium & production systems | Oracle, PG, MySQL, SQL Server | Credit, finance, regulatory, risk management |
| KingbaseES | Oracle migration & centralised DB replacement | Various banks’ production systems | Oracle, MySQL, SQL Server | Credit, credit card, finance, regulatory |
| Dameng | Domestic relational DB with complete ecosystem | Various banks’ production systems | Oracle and mainstream ecosystems | Core transactions, teller, credit, risk |
| TDSQL | Financial distributed core & cloud DB system | Medium‑large banks & core systems | MySQL, PG, Oracle | Credit card core, payments, accounting, internet channels |
Selection Recommendations: If a bank faces core transaction upgrades, Oracle replacement, and MySQL sharding governance simultaneously, OceanBase is worth prioritising in the PoC list. If domestic adaptation, localised service, and traditional database operations are valued, Dameng should be considered. If already using Tencent Cloud or a financial cloud system, or if large‑scale credit card core project experience is valued, TDSQL is worth evaluating.
03｜AlmaLinux and Oracle Linux Release Security Updates: PostgreSQL and MySQL Multiple High‑Risk CVEs Fixed
On July 2, AlmaLinux released a batch of security updates for critical infrastructure software on OS versions 8, 9, and 10, fixing dozens of CVE vulnerabilities across components including the Linux kernel, Apache mod_http2, PostgreSQL, PHP 7.4, MySQL 8.4, and Valkey, most rated at “Important” severity.
PostgreSQL Security Update (ALSA-2026:26203) :
- CVE-2026-6475: Symbolic link path traversal in pg_basebackup and pg_rewind, could lead to operating system account hijacking.
- CVE-2026-6477: Buffer overflow in PostgreSQL libpq, allowing a server superuser to overwrite client stack memory.
- CVE-2026-6478: Covert timing side‑channel in MD5 password comparison, could lead to credential recovery.
- CVE-2026-6473: Integer overflow could lead to under‑allocation and out‑of‑bounds write.
On the same day, Oracle Linux also released similar security updates (ELSA-2026-27741), fixing multiple CVEs in PostgreSQL and other components.
- DBA Perspective: CVE-2026-6475 (pg_basebackup symbolic link path traversal) and CVE-2026-6477 (libpq buffer overflow) both require attention – the former threatens backup chain security, the latter allows a server superuser to attack clients. DBAs running PostgreSQL should check versions as soon as possible and include security updates such as ALSA-2026:26203 in the Q3 patch window. The synchronous updates from AlmaLinux and Oracle Linux also remind DBAs that regardless of which Linux distribution they use, they need to monitor upstream security announcements.
04｜PostgreSQL Ecosystem Tool credcheck v5.0 Released: PG 19 Support, Password Policy Management Enhanced
On July 5, HexaCluster released version 5.0 of the credcheck PostgreSQL extension. The extension performs general credential checks during user creation, password changes, and user renaming, supporting custom rule sets:
- Allow/deny specific types of credentials.
- Reject easily guessable passwords.
- Enforce a minimum password validity period.
- Define password reuse policies.
- Define authentication failure limits and delays.
- Force password change on first login.
- Issue a warning N days before password expiry.
v5.0 Core Enhancements: Added compatibility with PostgreSQL v19, and made password history replication‑aware. Upgrading requires a PostgreSQL restart to reload the credcheck library.
- DBA Perspective: credcheck v5.0’s support for PG 19 ensures that DBAs can continue using password policy management after upgrading to PG 19. “Replication‑aware password history” means that in master‑slave replication environments, password history policies can be kept consistent across all nodes, avoiding the risk of policy failure after failover.
05｜Domestic Database Replacement Accelerates in Manufacturing and Water Conservancy: Kingware Releases Consecutive Industry Solutions
On July 5‑6, CETC Kingware consecutively released database solutions for the manufacturing and water conservancy industries. Kingware noted that manufacturing database technology will undergo a profound transformation from “relational single‑point” to “distributed collaboration” over the next 1‑3 years, with distributed architecture, hybrid workload processing, and autonomous control compliance becoming the three core drivers. In the water conservancy industry, Kingware predicts that with the advancement of smart water systems, water data will experience explosive growth, placing higher demands on time‑series data processing capability, cross‑regional data collaboration, and real‑time analysis.
KingbaseES V9 provides a solution path covering T‑SQL syntax compatibility (stored procedures, triggers, specific functions), KES Sharding for horizontal scaling to support PB‑level data, KES RAC and KES ADC to achieve RPO=0/RTO<30s high availability, and cross‑regional distributed multi‑active architecture. Additionally, Kingware released a MySQL migration solution, emphasising that “kernel‑level compatibility” is the cornerstone of building an autonomous ecosystem – KingbaseES V9 has a 100% proprietary intellectual property kernel, with 100% code autonomy, ensuring full‑stack adaptation capability in domestic software and hardware environments.
- DBA Perspective: Kingware’s consecutive publications in manufacturing, water conservancy, and MySQL migration directions reflect that domestic databases are expanding from “financial Xinchuang” to broader industries such as manufacturing and water conservancy. For DBAs, the breadth of industry Xinchuang is expanding. Mastering KingbaseES V9’s compatibility and high‑availability configurations across multiple scenarios will become a passport to cross‑industry Xinchuang projects.
📚 SQL Little Knowledge Point
This Issue’s Knowledge Point: What is HTAP (Hybrid Transaction/Analytical Processing)?
HTAP (Hybrid Transaction/Analytical Processing) is a database architecture that allows a single system to handle both OLTP (online transaction processing) and OLAP (online analytical processing) workloads simultaneously.
Traditional Architecture vs. HTAP:
| Dimension | Traditional Separated Architecture (OLTP + OLAP) | HTAP Integrated Architecture |
|---|---|---|
| Number of Systems | Two independent systems | One system |
| Data Sync | Scheduled ETL with latency | Native consistency, no latency |
| Operations Complexity | High (independent maintenance of two systems) | Low (unified management) |
| Real‑Time Analytics | Dependent on ETL cycles, non‑real‑time | Real‑time analytics on transactional data |
| Typical Scenarios | Traditional enterprise architecture | Smart manufacturing, real‑time risk control |
Why Manufacturing Scenarios Need HTAP:
- Modern factories generate tens of thousands of device writes per second while requiring minute‑level production reports.
- Traditional OLTP+OLAP separated architecture cannot meet real‑time requirements.
- HTAP handles both transactions and real‑time analytics within the same system, eliminating ETL latency.
KingbaseES V9 supports HTAP hybrid workloads through row‑column hybrid storage and integrated transaction/analytics processing.
HiddenMerit Team Production Slogan: 绩优隐于内，金石启新程 | Hidden deep. Merit bold. Forge ahead.
