OrioleDB beta14 is published! 🎉
github.com/orioledb/orioledb…
OrioleDB engine for PostgreSQL retweeted
OrioleDB is our next-gen storage extension for Postgres
we just added a feature so that you can rewind your database to a specified timestamp
OrioleDB engine for PostgreSQL retweeted
Replying to @kiwicopple
I’ve been running a long running test for a year with OrioleDB, I’ve been impressed so far!
OrioleDB engine for PostgreSQL retweeted
Scaling Postgres 383 is released! In this episode, we discuss the free availability of an OrioleDB patent, pgEdge going open source, pg_duckdb hitting 1.0 and methods resolve to slow order by limit queries: scalingpostgres.com/episodes… #Postgres #PostgreSQL
OrioleDB engine for PostgreSQL retweeted
The best conf of the year is almost at full capacity!
Secure your seat: select.supabase.com
OrioleDB engine for PostgreSQL retweeted
Today we are making the @orioledb Patent freely available to the Postgres community
Oriole is a storage extension for Postgres which uses Postgres' pluggable storage system. It's a drop-in replacement for Postgres' existing storage engine (Heap).
Our north star is to upstream Oriole to be part of the Postgres source tree, developed and maintained in the open alongside the rest of Postgres (if the community want it!)
We announced the acquisition of Oriole over a year ago. Since then, we have been working on cleaning up the legal structure and finalizing the asset transfers.
We have wrapped up all legal activities, and we fully own US Patent 10,325,030 (“Durable multiversion B+-tree”).
@supabase is making this Patent explicitly available to all Oriole users (including proprietary forks) in accordance with the open source license.
Oriole benchmarks show that it is around 5.5x faster than the default storage engine (Heap):
OrioleDB engine for PostgreSQL retweeted
Scaling Postgres 380 is released! In this episode, we discuss enhancements to Oriole DB, new Postgres releases, a logging guide and application framework frustrations: scalingpostgres.com/episodes… #Postgres #PostgreSQL
OrioleDB engine for PostgreSQL retweeted
30 days later and we're now ingesting up to 500K logs/second
nitter.cf/kiwicopple/status/1943…
Replying to @supabase
@supabase telemetry is getting a major update
- ingesting >300K logs per second, powered by @elixirlang
- soon shipping everything to @ClickHouseDB
- we're bullish on OTel
OrioleDB engine for PostgreSQL retweeted
Alexander Korotkov: Ordered Insertion Optimization in OrioleDB postgr.es/p/7b4
OrioleDB engine for PostgreSQL retweeted
new article from @ssougou on Postgres HA and how it will be handled in @multigres :
multigres.com/blog/postgres-…
OrioleDB engine for PostgreSQL retweeted
Alexander Korotkov: OrioleDB fastpath search postgr.es/p/79Y
OrioleDB engine for PostgreSQL retweeted
New @orioledb release: we added TPC-C benchmarks so you can be the judge on the performance
In case you're new to Oriole: it's a Postgres extension that replaces the default storage engine. GA coming soon.
OrioleDB engine for PostgreSQL retweeted
Joining Supabase
For some time, I've been considering a Vitess adaptation for Postgres, and this feeling had been gradually intensifying. The recent explosion in the popularity of Postgres has fueled this into a full-blown obsession. As these databases grow, users are going to face a hard limit once they max out the biggest available machine.
The project to address this problem must begin now, and I'm convinced that Vitess provides the most promising foundation. After exploring various environments, I found the best fit with Supabase. I’m grateful for how they welcomed me. Furthermore, their open-source mindset, fully remote work culture, and, most importantly, the empathetic leadership of @kiwicopple resonated with me.
Now, it’s time to make this happen.
Regarding PlanetScale
You might wonder why I didn’t consider building this at PlanetScale. After nearly three years away, I've come to recognize that it’s a different company now, with its own priorities and vision. I had to draw a line. It required some introspection, but I finally shifted my perspective from "What should the co-founder of PlanetScale do?" to "What should the co-creator of Vitess do?". Once I framed the question this way, the answer became clear.
OrioleDB engine for PostgreSQL retweeted
The tech stack I use to build my SaaS products making almost $7k+/mo:
Frontend - @nextjs ($20/mo)
Backend - @nextjs
Database - @supabase ($30/mo)
Authentication - @supabase
Deployment - @vercel
UI Kit - @chakra_ui / @shadcn
State management - @tan_stack
Customer Support - @crisp_im
User feedback - @featuresvote
Change logs - @featuresvote
Sending emails - @resend
AI assistant - @cursor_ai ($20/mo)
OrioleDB engine for PostgreSQL retweeted
A more technical post on the differences between Oriole and Neon on the @orioledb site:





















