Writing a Postgres logical replication system in Golang
1–10 of 21 posts
Re: Writing a Postgres logical replication system in Golang
#2Isn't that what others like Supabase are already offering or am I missing a distinction here?
Re: Writing a Postgres logical replication system in Golang
#3[0] - https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fww...
Re: Writing a Postgres logical replication system in Golang
#4If anyone from DoltHub team is reading this, please consider fixing [0] the RSS/Atom feed link [1]. I love your blog posts, but I am not able to subscribe to them in my feed reader. Your posts on SwissTable and Prolly Trees are my fav ones. [0] - https://validator.w3.org/feed/check.cgi?url=https%3A%2F%2Fww... [1] - https://www.dolthub.com/blog/rss.xml
Re: Writing a Postgres logical replication system in Golang
#5> the world's first version-controlled SQL database Isn't that what others like Supabase are already offering or am I missing a distinction here?
Re: Writing a Postgres logical replication system in Golang
#6> the world's first version-controlled SQL database Isn't that what others like Supabase are already offering or am I missing a distinction here?
Re: Writing a Postgres logical replication system in Golang
#7Re: Writing a Postgres logical replication system in Golang
#8> the world's first version-controlled SQL database Isn't that what others like Supabase are already offering or am I missing a distinction here?
Supabase offers version controlled database? To be clear, what dolt does is enabling you to branch like git and then merge your branch, rollback old "commits" of your database and similar stuff. It is much more advanced than audit logging
Re: Writing a Postgres logical replication system in Golang
#9News from the future? Who cares about causality?
Re: Writing a Postgres logical replication system in Golang
#10March 08, 2024. News from the future? Who cares about causality?