Hacker News: baotiaohttps://news.ycombinator.com/user?id=baotiaoHacker News RSShttps://hnrss.org/hnrss v2.1.1Tue, 28 Apr 2026 23:47:21 +0000<![CDATA[New comment by baotiao in "[dead]"]]>In 2026, Can AI Modify Database Kernel Code? Rewriting PostgreSQL with Claude Code: Full Page Write vs Doublewrite Buffer, a 3x Performance Gap

]]>Sun, 08 Feb 2026 23:49:44 +0000https://news.ycombinator.com/item?id=46939834baotiaohttps://news.ycombinator.com/item?id=46939834https://news.ycombinator.com/item?id=46939834<![CDATA[New comment by baotiao in "AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines"]]>Yes, MySQL-DuckDB columned read only node will continuously get data from transactional workload by binlog. Then people will not need to maintain tools like kafka/debezium to sync between two node.

]]>Fri, 06 Feb 2026 23:13:29 +0000https://news.ycombinator.com/item?id=46919453baotiaohttps://news.ycombinator.com/item?id=46919453https://news.ycombinator.com/item?id=46919453<![CDATA[New comment by baotiao in "AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines"]]>I’m quite certain that if DuckDB had been open-sourced and reached stability around 2020, TiDB would have definitely chosen DuckDB instead of ClickHouse.

]]>Wed, 04 Feb 2026 21:12:43 +0000https://news.ycombinator.com/item?id=46891853baotiaohttps://news.ycombinator.com/item?id=46891853https://news.ycombinator.com/item?id=46891853<![CDATA[New comment by baotiao in "AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines"]]>We havn't try that before, maybe I will try to combine with mysql-operator later..

]]>Wed, 04 Feb 2026 21:11:01 +0000https://news.ycombinator.com/item?id=46891830baotiaohttps://news.ycombinator.com/item?id=46891830https://news.ycombinator.com/item?id=46891830<![CDATA[New comment by baotiao in "AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines"]]>Actually, that’s not the case. I also support PostgreSQL products in my professional work. However, specifically regarding this issue—as I mentioned in my article—it is simply easier to integrate DuckDB by leveraging MySQL's binlog and its pluggable storage engine architecture.

]]>Wed, 04 Feb 2026 21:09:00 +0000https://news.ycombinator.com/item?id=46891802baotiaohttps://news.ycombinator.com/item?id=46891802https://news.ycombinator.com/item?id=46891802<![CDATA[Why MySQL's Integration with DuckDB Is More Elegant Than PostgreSQL's]]>Article URL: https://www.linkedin.com/top-content/

Comments URL: https://news.ycombinator.com/item?id=46887089

Points: 1

# Comments: 0

]]>Wed, 04 Feb 2026 15:35:09 +0000https://www.linkedin.com/top-content/baotiaohttps://news.ycombinator.com/item?id=46887089https://news.ycombinator.com/item?id=46887089<![CDATA[New comment by baotiao in "AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines"]]>Here is the professional English translation of your analysis, optimized for a technical audience or a blog post:

Why I Believe MySQL is More Suited than PostgreSQL for DuckDB Integration Currently, there are three mainstream solutions in the ecosystem: pg_duckdb, pg_mooncake, and pg_lake. However, they face several critical hurdles. First, PostgreSQL's logical replication is not mature enough—falling far behind the robustness of its physical replication—making it difficult to reliably connect a PG primary node to a DuckDB read-only replica via logical streams.

Furthermore, PostgreSQL lacks a truly mature pluggable storage engine architecture. While it provides the Table Access Method as an interface, it does not offer standardized support for primary-replica replication or Crash Recovery at the interface level. This makes it challenging to guarantee data consistency in many production scenarios.

MySQL, however, solves these issues elegantly:

Native Pluggable Architecture: MySQL was born with a pluggable storage engine design. Historically, MySQL pivoted from MyISAM to InnoDB as the default engine specifically to leverage InnoDB's row-level MVCC. While previous columnar attempts like InfoBright existed, they didn't reach mass adoption. Adding DuckDB as a native columnar engine in MySQL is a natural progression. It eliminates the need for "workaround" architectures seen in PostgreSQL, where data must first be written to a row-store before being converted into a columnar format.

The Power of the Binlog Ecosystem: MySQL’s "dual-log" mechanism (Binlog and Redo Log) is a double-edged sword; while it impacts raw write performance, the Binlog provides unparalleled support for the broader data ecosystem. By providing a clean stream of data changes, it facilitates seamless replication to downstream systems. This is precisely why OLAP solutions like ClickHouse, StarRocks, and SelectDB have flourished within the MySQL ecosystem.

Seamless HTAP Integration: When using DuckDB as a MySQL storage engine, the Binlog ecosystem remains fully compatible and intact. This allows the system to function as a data warehouse node that can still "egress" its own Binlog. In an HTAP (Hybrid Transactional/Analytical Processing) scenario, a primary MySQL node using InnoDB can stream Binlog directly to a downstream MySQL node using the DuckDB engine, achieving a perfectly compatible and fluid data pipeline.

]]>Wed, 04 Feb 2026 07:35:16 +0000https://news.ycombinator.com/item?id=46882662baotiaohttps://news.ycombinator.com/item?id=46882662https://news.ycombinator.com/item?id=46882662<![CDATA[New comment by baotiao in "AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines"]]>On this page, we introduce how to implement a read-only Columnar Store (DuckDB) node leveraging the MySQL binlog mechanism. https://github.com/alibaba/AliSQL/blob/master/wiki/duckdb/du... In this implementation, we have performed extensive optimizations for binlog batch transmission, write operations, and more.

]]>Wed, 04 Feb 2026 07:25:33 +0000https://news.ycombinator.com/item?id=46882597baotiaohttps://news.ycombinator.com/item?id=46882597https://news.ycombinator.com/item?id=46882597<![CDATA[AliSQL: Alibaba's open-source MySQL with vector and DuckDB engines]]>Article URL: https://github.com/alibaba/AliSQL

Comments URL: https://news.ycombinator.com/item?id=46875228

Points: 306

# Comments: 49

]]>Tue, 03 Feb 2026 18:40:18 +0000https://github.com/alibaba/AliSQLbaotiaohttps://news.ycombinator.com/item?id=46875228https://news.ycombinator.com/item?id=46875228<![CDATA[New comment by baotiao in "Ask HN: Could you share your personal blog here?"]]>http://baotiao.github.io/

130 blog posts. Writing about Database and Distributed system

]]>Tue, 04 Jul 2023 17:51:39 +0000https://news.ycombinator.com/item?id=36590197baotiaohttps://news.ycombinator.com/item?id=36590197https://news.ycombinator.com/item?id=36590197<![CDATA[New comment by baotiao in "Boost:Unordered_flat_map"]]>Inside boost::unordered_flat_map

]]>Sun, 04 Dec 2022 20:00:18 +0000https://news.ycombinator.com/item?id=33857220baotiaohttps://news.ycombinator.com/item?id=33857220https://news.ycombinator.com/item?id=33857220<![CDATA[Boost:Unordered_flat_map]]>Article URL: http://bannalia.blogspot.com/2022/11/

Comments URL: https://news.ycombinator.com/item?id=33857219

Points: 2

# Comments: 1

]]>Sun, 04 Dec 2022 20:00:18 +0000http://bannalia.blogspot.com/2022/11/baotiaohttps://news.ycombinator.com/item?id=33857219https://news.ycombinator.com/item?id=33857219<![CDATA[Coding for SSDs]]>Article URL: https://codecapsule.com/2014/02/12/coding-for-ssds-part-1-introduction-and-table-of-contents/

Comments URL: https://news.ycombinator.com/item?id=28455868

Points: 2

# Comments: 1

]]>Wed, 08 Sep 2021 12:07:50 +0000https://codecapsule.com/2014/02/12/coding-for-ssds-part-1-introduction-and-table-of-contents/baotiaohttps://news.ycombinator.com/item?id=28455868https://news.ycombinator.com/item?id=28455868<![CDATA[Evolution of tree data structures for indexing]]>Article URL: https://erthalion.info/2020/11/28/evolution-of-btree-index-am

Comments URL: https://news.ycombinator.com/item?id=27963753

Points: 101

# Comments: 12

]]>Mon, 26 Jul 2021 19:01:29 +0000https://erthalion.info/2020/11/28/evolution-of-btree-index-ambaotiaohttps://news.ycombinator.com/item?id=27963753https://news.ycombinator.com/item?id=27963753<![CDATA[New comment by baotiao in "PolarFS: Alibaba Distributed File System for Shared Storage Cloud Database [pdf]"]]>I think the most interesting part is PolarFS taking full advantage of the emerging techniques like RDMA, NVMe, and SPDK. And the Parallel raft consensus algorithm

]]>Wed, 22 Aug 2018 12:56:53 +0000https://news.ycombinator.com/item?id=17818349baotiaohttps://news.ycombinator.com/item?id=17818349https://news.ycombinator.com/item?id=17818349<![CDATA[New comment by baotiao in "PolarFS: Alibaba Distributed File System for Shared Storage Cloud Database [pdf]"]]>Yes I am from the PolarFS team. You can read from the paper that we have compared PolarFS with ceph.

]]>Wed, 22 Aug 2018 12:25:03 +0000https://news.ycombinator.com/item?id=17818165baotiaohttps://news.ycombinator.com/item?id=17818165https://news.ycombinator.com/item?id=17818165<![CDATA[New comment by baotiao in "PolarFS: Alibaba Distributed File System for Shared Storage Cloud Database [pdf]"]]>The protocol is interesting, and we will provide the TLA+ proof soon.

]]>Wed, 22 Aug 2018 05:14:46 +0000https://news.ycombinator.com/item?id=17816477baotiaohttps://news.ycombinator.com/item?id=17816477https://news.ycombinator.com/item?id=17816477<![CDATA[New comment by baotiao in "PolarFS: Alibaba Distributed File System for Shared Storage Cloud Database [pdf]"]]>Thank you. We will provide our TLA+ proof soon..

]]>Wed, 22 Aug 2018 05:08:13 +0000https://news.ycombinator.com/item?id=17816456baotiaohttps://news.ycombinator.com/item?id=17816456https://news.ycombinator.com/item?id=17816456<![CDATA[Optimizing Paxos with batching and pipelining (2012) [pdf]]]>Article URL: https://pdfs.semanticscholar.org/a0d0/cdd2e8af1945c03cfaf2cb451f71f208d0c9.pdf

Comments URL: https://news.ycombinator.com/item?id=16952649

Points: 71

# Comments: 1

]]>Sun, 29 Apr 2018 16:22:03 +0000https://pdfs.semanticscholar.org/a0d0/cdd2e8af1945c03cfaf2cb451f71f208d0c9.pdfbaotiaohttps://news.ycombinator.com/item?id=16952649https://news.ycombinator.com/item?id=16952649<![CDATA[Fpaxos]]>Article URL: https://fpaxos.github.io/

Comments URL: https://news.ycombinator.com/item?id=16047258

Points: 1

# Comments: 0

]]>Mon, 01 Jan 2018 18:29:16 +0000https://fpaxos.github.io/baotiaohttps://news.ycombinator.com/item?id=16047258https://news.ycombinator.com/item?id=16047258