I'm re-releasing the generalized consensus series one blog at a time for easier ingestion. Today, it will be the first two parts: Defining the Problem and Setting the Requirements. Links in ๐งต
If a transaction was acknowledged as successful, multigres will guarantee preservation. If you issued a commit and it just timed out, the outcome is unknown. This is the case for a single node postgres also.
IOW, depending on circumstances, that transaction may or may not be preserved.
Multigres is now in private alpha: high availability for Supabase Postgres. If your database fails, a standby copy takes over on its own, and data your app already saved is not lost.
Organizations on paid plans can request access.
Learn more โ https://t.co/5mUOaPNxwX
i had 12 Claude agents running in parallel for 6 hours and i managed to reverse engineer @supabase
i'm making it available here so that you can save your tokens - 100% free & open-source:
https://t.co/uA7zj7SCV9
I chatted with @ATechGirl from @supabase on her 25 years of experience as a developer, her time as the project lead of Vitess, her work on Multigres, and databases at Supabase in general.
No paywall, give it a read.
https://t.co/srYwZyHLaA
This is a postgres compatible connection pooler where you're free to interleave connection state altering statements like create temp table, set variables, etc.
in the Postgres ecosystem there are a lot of tools that are "postgres compatible"
one of the design goals for Multigres is compatibility - allowing you to scale up without any trade-offs.
@multigres has now achieved 100% pass-rate on all major Postgres test suites: