Skip to main content
Alicloud’s rds_duckdb: Tribute or Rip-Off?
  1. Cloud-Exit/

Alicloud’s rds_duckdb: Tribute or Rip-Off?

·739 words·4 mins· ·
Ruohang Feng
Author
Ruohang Feng
Pigsty Founder, @Vonng
Table of Contents

A viral post titled “Heavenly ‘PostgreSQL’ Calls Earthly Postgres ‘Little Trash’” hyped up Alicloud RDS’s new rds_duckdb plugin for OLAP and declared that managed RDS PG is noble while open-source Postgres is garbage. That take is ridiculous.

I know DuckDB and the derivative pg_duckdb extension inside out. I’m happy when cloud vendors integrate open source legally and respectfully. But if you disparage the upstream while riding on its work, someone has to push back.


PG + DuckDB, the background
#

DuckDB is a fast embedded OLAP database I’ve followed for years. In “PostgreSQL Is Eating the Database World” I talked about welding DuckDB onto PG to build true HTAP, and that article sparked a worldwide trend. 2024 saw multiple PG extensions that embed DuckDB; it was one of the year’s signature moves.

Among those experiments, pg_duckdb—co-developed by MotherDuck and Hydras’ OLAP startup—is the most promising. I packaged it for EL8/9, Debian 12, Ubuntu 22/24, both x86 and ARM, and spent countless hours testing it.

Out of the 200+ PG extensions I maintain, the four DuckDB-related ones (including pg_mooncake, built atop pg_duckdb) are both the most painful and the most exciting: huge dependencies, gnarly build chains, multiple libduckdb versions, cross-platform PG support. But OLTP + OLAP fusion is worth the pain.


Tribute or plagiarism?
#

When Alicloud launched rds_duckdb last October, my first reaction was “cool, adoption!” Two months after pg_duckdb went public, a cloud vendor followed suit—that helps the industry.

But rds_duckdb isn’t open source, so we can’t inspect its code. We can only observe behavior, and the surface looks… familiar. Early pg_duckdb exposed a single switch: SET pg_duckdb.execution = on; and boom, DuckDB queries over PG tables. rds_duckdb’s centerpiece? SET rds_duckdb.execution = on;. Same flow, different prefix.

Given the timing (two months gap) and the identical UX, it’s reasonable to assume heavy inspiration at minimum. Maybe the code is different—we can’t tell because it’s closed. They added some extra functions (copy data, show sizes, PG 12/13 support), but nothing groundbreaking. Honestly it looks like a prototype compared to later pg_duckdb builds or pg_mooncake. If you’re going to plagiarize, at least do it well.

And if it’s a “tribute,” where’s the attribution? No credits to pg_duckdb or even DuckDB anywhere.


Obligations under MIT
#

Both DuckDB and pg_duckdb are MIT licensed. The requirements are simple: keep the copyright notice and include the MIT license text. It’s literally “use the code for free, just don’t erase our names.”

I scoured Alicloud’s RDS docs and couldn’t find DuckDB’s copyright notice or license anywhere. If rds_duckdb doesn’t reuse code, fine. But if it does, omitting attribution violates MIT before we even talk about morals.


Attacking open source
#

I don’t know whether that WeChat account coordinates with Alicloud, but their anti-open-source streak is obvious. Recent posts include calling Postgres “little trash,” saying “cloud-native DBs destroyed Kubernetes self-managed databases,” and “open source is a scam.”

This bias is absurd. Open source is why foundational software exists at all. DeepSeek’s breakthrough? Standing on open shoulders. Postgres’s rise? Same story. Most “cloud databases” are just open-source engines with proprietary duct tape. Without OSS, their products wouldn’t exist.

Yet hyperscalers rake in profits and rarely give back, igniting debates about “clouds freeloading on open source” and the tensions keep rising. Some vendors do contribute—AWS helped make pgvector the de facto standard and released log_fdw, pgcollection, pgtle, etc.

Alicloud, however, seems stuck in “eat from the OSS/Startup bowl” mode. The manners are rough, the product quality is embarrassing, and customers end up thinking the whole thing is a clown show. Users aren’t mad that clouds use open source; they’re mad when a giant ships a half-baked clone, sneers at the upstream, and calls it innovation.


Further reading
#

Grassroots Circus: Alicloud RDS Crashed Again

Is Cloud Storage a Pig-Butchering Scam?

Is a Cloud Database Just a Tax on IQ?

Alicloud’s High-Availability Myth Shattered

From Cost Cutting to Actual Efficiency Gains

Lessons From Alicloud’s Epic Failure

Alipay Down Again During Double-11

Alicloud DCDN Racked Up ¥1,600 in 32 Seconds

Forecast: This Alicloud Incident Will Last 20 Years

Alicloud Singapore AZ-C Fire

Another Alicloud Outage—Was It a Fiber Cut?

Cloud Computing: Mediocrity Is Original Sin

taobao.com Certificate Expired

Stop Worshipping Toothpaste Clouds

Luo Yonghao Can’t Save Toothpaste Cloud

Young People Lost Inside Alicloud

Does Alicloud’s Price Cut Actually Cut Costs?

Alicloud Weekly: Database Control Plane Down Again

Alicloud’s Epic Crash, Again

How Cloud Vendors See Customers: Broke, Idle, Needy

Related

Whoever Integrates DuckDB Best Wins the OLAP World

·1322 words·7 mins
Just like the vector database extension race two years ago, the current PostgreSQL ecosystem extension competition has begun revolving around DuckDB. MotherDuck’s official entry into the PostgreSQL extension space undoubtedly signals that competition has entered white-hot territory.