mmontagna9

If you're interested in using them you should just bench them yourself.

Aren't we all...

People run postgres at scale which is much "larger" than what you are running, which isn't to say that your workload isn't substantial, it is. But there are folks who push it harder, both in terms of writes/rows and workload complexity. It's one thing to write a ton of rows into a single table, it's another thing entirely to write into many tables, index all of them and then query them at scale; you didn't mention much about your workload complexity so I'm not trying to suggest it isn't complex, but there are certainly plenty of folks on this forum who can attest to it being tricky to scale high write workloads, in large organizations with many stakeholders and complex query loads.

The youngest old man I know at any rate

Managing one pair of headphones that connects to more than one device is a nightmare, everything always auto connects/disconnects when you don't want. Many devices don't have a temporarily disable connection attempts toggle.

Sadly this isn't true. Postgres will happily replicate and skip data if you tell it too.

And there have been multiple bugs around logical replication in version ~10-15 that can cause data loss. None of these are directly related to lsn fiddling tho.

You caught our off by one bug :)

Where are you getting your numbers?!

Yeah there isn't much publically available. We wrote a tool for this at Instacart, it relies on some internal tooling but much of it is generalizable (assuming you run pgbouncers). This is a good reminder for us to write a blog post or something.

Needs a clearly marked manual kill switch

> Reduced maintenance needs. OrioleDB implements the concepts of undo log and page-mergins, eliminating the need for dedicated garbage collection processes. Additionally, OrioleDB implements default 64-bit transaction identifiers, thus eliminating the well-known and painful wraparound problem.

I love this, no more vacuums?

> In my experience, PG is always the most out-of-date piece of any system.

Yes

Some shops don't design like that :) some folks build giant monoliths and then have to scale/deploy that app with it's database connections broadly.

Yep the readme is pretty clear it's a POC "Alpha: don't use in production just yet."

That said I've struggled with more than my fair share of pgbouncer misconfigurations and outright bugs. I personally would love a simpler (harder to misconfigure) and less buggy alternative.

This is great. Let me know how I can help