43 points | by handfuloflight an hour ago ago
5 comments
Pretty exciting to see a sharded Postgres product in the market.
The pitch is compelling. I wonder how many teams will be able to operate sharded database setups in production as a result of this.
I see no mention of foreign keys, or any other constraints, across shards. If, as I suspect, they're not implemented, it would still be useful but at the level of Spanner 10 years ago.
Cross shard transactions are “coming soon”. So, this is just like having multiple postgres clusters.
Cross shard transactions are supported, but we don't have support for atomic 2pc cross shard transactions, its WIP
Some more discussion: https://news.ycombinator.com/item?id=49645686
Pretty exciting to see a sharded Postgres product in the market.
The pitch is compelling. I wonder how many teams will be able to operate sharded database setups in production as a result of this.
I see no mention of foreign keys, or any other constraints, across shards. If, as I suspect, they're not implemented, it would still be useful but at the level of Spanner 10 years ago.
Cross shard transactions are “coming soon”. So, this is just like having multiple postgres clusters.
Cross shard transactions are supported, but we don't have support for atomic 2pc cross shard transactions, its WIP
Some more discussion: https://news.ycombinator.com/item?id=49645686