Viewing profile — akorotkov

We keep going. Planning GA till the end of this year. Only a couple of missing features left. The main focus is stability.

Exclusion constraints should work well for this case. On any transaction isolation level. https://www.postgresql.org/docs/current/ddl-constraints.html...

We will eventually add the SERIALIZABLE isolation level to OrioleDB, but right now that's not our highest priority. Let me explain why. At first, SSI (serializable snapshot isolati…

Yep, regular PostgreSQL indexes point to a heap location (block number + offset). And it is the same for primary and secondary indexes.

Thank you, that would be on the TODO list.

This 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 buff…

Hey HN, I'm the creator of OrioleDB, an extension for PostgreSQL that serves as a drop-in replacement for the default Heap storage engine. It is designed to address scalability bot…

We're planning to reach GA this year. Pushing all the patches to PostgreSQL core and making OrioleDB a pure extension will take more time.

Currently, 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 …

Hey HN, I'm the creator of OrioleDB, an extension for PostgreSQL that serves as a drop-in replacement for the default Heap storage engine. It is designed to address scalability bot…

Additionally, OrioleDB beta12 features a new fastpath tree search, which can accelerate workloads with intensive key-value lookups by up to 20%. Stay tuned for a new blog post abou…

Hey HN, I'm the creator of OrioleDB, an extension for PostgreSQL that serves as a drop-in replacement for the default Heap storage engine. It is designed to address scalability bot…

> That kind of exists thanks to NeonDB? This is unrelated to NeonDB. OrioleDB has been acquired by Supabase. https://supabase.com/blog/supabase-acquires-oriole

> OrioleDB solve the vacuum problem with the introduction of the undo log. Way more than just this! > With some work you can run OrioleDB AND neon storage and get benefits of both.…

That's also so cool we are getting externally validated! https://x.com/MinisterOfEng/status/1864793214282019065 My kudos to MinisterOfEng!

> Additionally, PostgreSQL requires N^2 of memory depending on the number of connections, For sure, not all the PostgreSQL memory is N^2. AFAIR, just a couple of components, includ…

Thank you for your feedback! We tried to enable think time with go-tpc, thanks to @pashkinelfe. That leaves us with 1 tpmC per connection, growing linearly up to ~300 connections f…

Thank you, your feedback is appreciated. The important design issue about building active-active multi-master on the base of raft protocol is about being able to apply changes loca…

Some notable benchmarks from the OrioleDB beta7 release: * 5.5x Faster at 500 Warehouses: In TPC-C benchmarks with 500 warehouses, OrioleDB outperformed PostgreSQL's default heap t…

This was driven by Andres Freund for pg12. Please, check this. https://anarazel.de/talks/2018-10-25-pgconfeu-pluggable-stor... However, the current table AM API in many aspects ass…