Top all-time · #2860
OrioleDB Blog
Company blog · orioledb.com/blogdatasystems
OrioleDB Blog is the company blog at orioledb.com, writing about data and systems. Since 2024, 27 different Hacker News readers have linked it 45 times, most often “OrioleDB: next generation storage engine for PostgreSQL”. It is still writing: the last post was on 2026-07-06, and you can follow it by feed.
Too few sampled comments (18) to say how often HN recommends it.?
Why HN links it
HN commenters link OrioleDB's blog and docs as the reference for this Postgres storage engine extension, which Supabase now works on. Linked topics include patches, beta releases, benchmarks, bridged indexes and vacuum-free storage.
Summarised by Claude from a sample of 18 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
OrioleDB is a PostgreSQL extension that combines the advantages of both on-disk and in-memory engines.
Most-linked posts?
- OrioleDB: next generation storage engine for PostgreSQL6 people · 6 mentions · first linked 2024-04-16
- Why PostgreSQL needs a better API for alternative table engines?4 people · 4 mentions · first linked 2025-03-24
- The differences between OrioleDB and Neon4 people · 4 mentions · first linked 2025-06-20
- Ordered Insertion Optimization in OrioleDB3 people · 3 mentions · first linked 2025-08-19
- /docs3 people · 3 mentions · first linked 2025-01-10
- Show HN: OrioleDB Beta12 Features and Benchmarks2 people · 2 mentions · first linked 2025-07-15
- OrioleDB beta7: Benchmarks2 people · 2 mentions · first linked 2024-12-01
- Bridged Indexes in OrioleDB: architecture, internals and everyday use?2 people · 2 mentions · first linked 2025-05-30
- OrioleDB beta15 and beta16: stability, testing, and replication hardening2 people · 2 mentions · first linked 2026-07-29
- Rethinking PostgreSQL buffer mapping for modern hardware architectures2 people · 2 mentions · first linked 2024-05-21
What Hacker News says?
> OrioleDB tables don't support SERIALIZABLE isolation level. This is an unfortunate limitation to be aware of when evaluating https://www.orioledb.com/docs/usage/getting-started#current-...
Comment linking /docs/usage/getting-started
on “OrioleDB Patent: now freely available to the Postgres community”Submitted OrioleDB beta7: Benchmarks as a story · 140 points
HN discussionThis is generally true, but there are some additional aspects. 1. With PostgreSQL heap, you need to access the heap page itself. And it's not for free. It goes all through the buffer manager and other related components. 2. In OrioleDB, we have a lightweight protocol to read from pages. In-memory pages are connected using direct links ( https://www.orioledb.com/docs/architecture/overview#dual-poi... ), and pages are…
Comment linking /blog/orioledb-fastpath-search
on “OrioleDB Patent: now freely available to the Postgres community”Submitted Bridged Indexes in OrioleDB: architecture, internals and everyday use? as a story · 76 points
HN discussionWe are tracking the patches here: https://www.orioledb.com/docs#patch-set The actual storage engine is written as an extension - these patches are mostly to improve the TAM API. If these are accepted by the community then it should be simpler for anyone to write their own Storage extensions. I think (correctly) it will take a lot longer to upstream the extension - the PG community should take a “default no” attitude…
Comment linking /docs
on “OrioleDB Patent: now freely available to the Postgres community”Submitted Show HN: OrioleDB Beta12 Features and Benchmarks as a story · 55 points
HN discussionOreole is not a plug-and-play yet. From their docs ( https://www.orioledb.com/docs ) > OrioleDB currently requires a set of patches to PostgreSQL to enhance the pluggable storage API and other PostgreSQL subsystems. All of these patches have been submitted to the PostgreSQL community and are under review.
Comment linking /docs
on “OrioleDB Patent: now freely available to the Postgres community”Submitted Ordered Insertion Optimization in OrioleDB as a story · 19 points
HN discussionOrioleDB is new to me. According to the docs, it “uses Postgres Table Access Method (TAM) to provide a pluggable storage engine for PostgreSQL. […] Pluggable Storage gives developers the ability to use different storage engines for different tables within the same database. Developers will be able to choose a storage method that is optimized for their specific needs: some tables could be configured for high transact…
Comment linking /docs
on “OrioleDB Patent: now freely available to the Postgres community”Submitted Why PostgreSQL needs a better API for alternative table engines? as a story · 15 points
HN discussion"The differences between OrioleDB and Neon" ( June 20, 2025 ) https://www.orioledb.com/blog/orioledb-neon-differences
Comment linking /blog/orioledb-neon-differences
on “OrioleDB Patent: now freely available to the Postgres community”Submitted The differences between OrioleDB and Neon as a story · 13 points
HN discussion(I’m on the Supabase team) Oriole has joined us at supabase now and it’s being worked on full time by Alexander and his team. Here is the patch set: https://www.orioledb.com/docs#patch-set It will be available to try on the supabase platform later this year too
Comment linking /docs
on “MVCC – the part of PostgreSQL we hate the most (2023)”Submitted Postgres Engines; a Look at OrioleDB and Neon Divergences as a story · 6 points
HN discussionI don't want to hijack Datadogs+Quickwit's post comment section with unrelated promotional-looking info. Quick summary below but if you have any other questions pls tag olirice in a Supabase GH discussion. The OrioleDB storage engine for postgres is a drop-in replacement for the default heap method. Its takes advantage of modern hardware (e.g. SSDs) and cloud infrastructure. The most basic benefit is that throughput…
Comment linking /docs
on “Datadog acquires Quickwit”Submitted Rethinking PostgreSQL buffer mapping for modern hardware architectures as a story · 4 points
HN discussionIt's a bit sad that many modern databases were recently acquired. They had the potential to bring a lot of innovations. 1. https://www.warpstream.com/ 2. https://www.orioledb.com/ 3. https://quickwit.io/
Comment linking /
on “Datadog acquires Quickwit”Submitted Ordered Insertion Optimization in OrioleDB as a story · 4 points
HN discussionOrioleDB maintains a very small set of Postgres patches that are targeted for upstream. The storage engine that mitigates the need for vacuuming [1] is implemented in a standard Postgres extension, so that will still need to be installed by the Postgres host in order to take advantage of it. But yeah, looking forward to that day too! [1] https://www.orioledb.com/blog/no-more-vacuum-in-postgresql
Comment linking /blog/no-more-vacuum-in-postgresql
on “PostgreSQL is the Database Management System of the Year 2024”Submitted OrioleDB fastpath search (faster random key lookups for PostgreSQL) as a story · 4 points
HN discussionServerless in the context of Postgres means to decouple storage and compute, so you could scale compute "infinitely" without setting up replica servers. This is what Neon offers, where you can just keep hitting their endpoints with your pg client and it should just take whatever load (in principle) and bill you per request. Supabase gives you a server that runs classic Postgres in a process. Scaling in this scenario…
Comment linking /
on “Databricks in talks to acquire startup Neon for about $1B”Submitted Why PostgreSQL needs a better API for alternative table engines? as a story · 4 points
HN discussionThere is also this one from Supabase: https://www.orioledb.com/
Comment linking /
on “Snowflake to buy Crunchy Data for $250M”Submitted Why PostgreSQL needs a better API for alternative table engines? as a story · 3 points
HN discussionThere's an experimental feature which separates storage and compute. https://www.orioledb.com/docs/usage/decoupled-storage
Comment linking /docs/usage/decoupled-storage
on “Bridged Indexes in OrioleDB: architecture, internals and everyday use?”Submitted Rethinking PostgreSQL buffer mapping for modern hardware architectures as a story · 3 points
HN discussionCurrently, OrioleDB can use GIN indexes via index bridging mechanism. https://www.orioledb.com/blog/orioledb-bridged-indexes But more effective native analogues for GIN/RUN are in our roadmap.
Comment linking /blog/orioledb-bridged-indexes
on “Show HN: OrioleDB Beta12 Features and Benchmarks”Submitted Ordered Insertion Optimization in OrioleDB as a story · 2 points
HN discussion> But I wonder if the core team, which is famously quite conservative about introducing big changes, sees this as too different to adopt as a replacement we respect the level of conservatism in Postgres and expect that this could take a while to upstream. we're committed to any timeline and we'll develop it for self-hosters and on the supabase platform first to iron out all the bugs that said, even if it remains an…
Comment linking /docs
on “Show HN: OrioleDB Beta12 Features and Benchmarks”Submitted OrioleDB Beta12: Features and Benchmarks as a story · 2 points
HN discussion
