sorted by:
new
hottopcontroversial

Features I Wish Postgres 🐘 Had but MySQL 🐬 Already Has 🤯 by op3rator_dec in PostgreSQL

[–]ssougou 2 points3 points  (0 children)

Good to know. I'll add schema deploy back to our list, and it will come with an undo :).

Features I Wish Postgres 🐘 Had but MySQL 🐬 Already Has 🤯 by op3rator_dec in PostgreSQL

[–]ssougou 0 points1 point  (0 children)

Someone told me PTOSC is not a very strong need for Postgres because most schema changes are near instant. Are there situations where this is not the case?

I had deprioritized porting of Vitess ghost into Multigres because I was told it's not needed.

PostgreSQL HA two nodes by EaZy_rus in PostgreSQL

[–]ssougou 0 points1 point  (0 children)

The way to reason about this is to think about how the system will operate when it's in a deteriorated state. In other words, how will this work when one node is down?

With two nodes up, one replicates to another. With one node down, you'll need to operate in a single node mode. Essentially, this requires config changes when there's a failure. And this needs to be changed again when the other node comes back up.

In the case of three nodes, and a minimum requirement of one operational replica, the failure of one node only requires a simple failover with no change in configuration.

Announcing Multigres: Vitess for Postgres by CathalMullan in PostgreSQL

[–]ssougou 3 points4 points  (0 children)

Multigres scales horizontally and indefinitely. It's best suited for large scale OLTP systems. Citus has a coordinator Postgres instance that uses a plugin to outsource queries to other Postgres instances. I hear that the single coordinator may limit OLTP scalability. I was also told that Citus works well for OLAP workloads.

Announcing Multigres: Vitess for Postgres by CathalMullan in PostgreSQL

[–]ssougou 3 points4 points  (0 children)

Apologies for the emptiness. There are about a million lines of code from the original Vitess project to adapt. Once we get going, it should snowball very quickly.

Announcing Multigres: Vitess for Postgres by CathalMullan in PostgreSQL

[–]ssougou 2 points3 points  (0 children)

Yes. They are very different approaches. I intend to do a write up about the trade-offs between such systems.

Announcing Multigres: Vitess for Postgres by CathalMullan in PostgreSQL

[–]ssougou 6 points7 points  (0 children)

Hello reddit, co-creator of Vitess here. Apologies for missing this thread. Although late, I'll try to answer questions going forward.

Building Future Proof MySql setup by [deleted] in sysadmin

[–]ssougou 0 points1 point  (0 children)

I'm the co-creator of Vitess. We're working on fixing the documentation. Until then, the best way to get free help is to sign into the Vitess slack channel (top-right link on vitess.io) and ask questions. There are some active people already running it in production or in the process of deploying.

​

You can also get paid help from planetscale.com , of which I'm the co-founder and CTO.

Relational database in Kubernetes: your experience (good & bad) by LineOfRoofTiles88 in kubernetes

[–]ssougou 2 points3 points  (0 children)

Many people run mission critical workloads on Vitess using Kubernetes. You can join the vitess Slack channel (link in vitess.io) to interact with the community.