5 ms·

PostgreSQL Interface for Google Spanner

• londons_explore 4y ago
  It's disappointing that each database can only talk one SQL dialect. That means every application that accessed the database will have to use the same, and any migration will be a lot of work.
  • paulryanrogers 4y ago
    Sad there are so many dialects. Ideally each would converge on standard SQL and the standard would adopt enhancements as they become widespread. Much like vender prefixing in CSS. Then one wouldn't need bespoke features except temporarily or where they are truly necessary for the business.
  • Tostino 4y ago
    One potential way forward is what AWS is trying with their Babblefish project: https://babelfishpg.org/ https://babelfishpg.org/ If this proves successful, there could be other implementations for other vendor dbms dialects.
• ranguna 4y ago
  If you want to know the actual compatibility list first, instead of marketing speak, check out this link: https://cloud.google.com/spanner/docs/reference/postgresql/overview https://cloud.google.com/spanner/docs/reference/postgresql/o... Spoiler: no stored procedures or triggers, amongst other stuff.