You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Citus and pg_shard should be able to sync distribution metadata back and forth without any user intervention. Determine what approaches could meet this need.
The text was updated successfully, but these errors were encountered:
Citus' Select logic doesn't change a shard's (or shard placement's) metadata. So if a table is created and owned by pg_shard, we'll only need to support uni-directional metadata sync from pg_shard to CitusDB. If a table is owned by CitusDB, it's still an open question if a user would want to insert data into it through pg_shard.
Citus' Select doesn't need to change metadata because it recognizes failures in one of two ways:
The user updates the membership list in pg_worker_list.conf, and then sends PostgreSQL a SIGHUP. Citus won't send Select queries to nodes that aren't in the membership list.
If the shard placement is marked as inactive, Citus won't send a query to it.
Citus and pg_shard should be able to sync distribution metadata back and forth without any user intervention. Determine what approaches could meet this need.
The text was updated successfully, but these errors were encountered: