2 ms·
And then just one query comes along where you need to make an update that should be globally visible, and not just visible to the shard. I can see why you woul
by brandmeyer 6y ago
And then just one query comes along where you need to make an update that should be globally visible, and not just visible to the shard.
I can see why you would stick with full Postgres for as long as practicable.
- csharptwdec19 6y agoIf it's that global of an update, it's probably something that could be run as part of a schema migration and could just be handled during update rollout. If it's some form of state that needs a global update on the regular, it's likely a sign that your data is not sharded properly.