4 ms·
Agree on the callout. This one we are going to enable soon so it's fixable. So the correction is that it's architecturally possible, but temporarily disabled. H
by nikita 3y ago
Agree on the callout. This one we are going to enable soon so it's fixable. So the correction is that it's architecturally possible, but temporarily disabled. Hope we will be able to run Supabase on it soon!
Also there are some storage plugins that won't work b/c we take over Postgres low level storage.
- harshitgangal 3y agoLikewise in Vitess. It is architecturally possible to add 100% compatibility :)
- nikita 3y agoWell it’s much much harder. Query plans over the distributed system should be different and transaction coordination is different when queries span shards. It’s impossible to give 100% performance compatibility.
- shlomi-noach 3y agoVitess maintainer here. I feel like the discussion was about 100% feature (queries/protocol/...) compatibility and that somehow it shifted to 100% performance compatibility? 100% performance compatibility is trivially not something to claim.