Multigres: Vitess for Postgres

Re:Multigres: Vitess for Postgres by oliverrice on Tuesday June 10, 2025 @02:27PM (#44239792)

how are you thinking the differences between mysql and postgres will impact multigres vs vitess? The ones the jump to mind are

- Postgres has transactional DDL vs auto-commit. Can that property be retained?

- Postgres leans into extensions much more that Mysql. Will types/indexes/etc introduced by e.g. pg_vector or postgis, have a path for support?

anything similar that will be a challenge?

[ Parent | on HN ]

Re:Multigres: Vitess for Postgres by sougou on Tuesday June 10, 2025 @02:33PM (#44239862)

You won't believe what a nightmare it was to work with transactionless DDLs in MySQL. Transactional DDL will be a dream come true for Vitess: we can throw away all the hacks we had to do for MySQL's sake.

I also see such a clean 2PC API. This was another huge mess on the MySQL side.

[ Parent | on HN ]

Re:Multigres: Vitess for Postgres by hyper_cube on Tuesday June 10, 2025 @03:41PM (#44240619)

I am interested in the extension question too. What kind of challenge that will present.

[ Parent | on HN ]