Communication goals (e.g. detailed howto vs orientation)
We wrote an announcement blog post about deprecating this replication policy, when we launched Citus 5. We then wrote another blog post on this topic. After 6 years, these blog posts seem to have disappeared.
Why are we implementing it? (sales eng)
We deprecated citus.shard_replication_factor when we merged pg_shard into Citus. https://www.citusdata.com/blog/2016/12/15/citus-replication-model-today-and-tomorrow/
What are the typical use cases?
Communication goals (e.g. detailed howto vs orientation)
We wrote an announcement blog post about deprecating this replication policy, when we launched Citus 5. We then wrote another blog post on this topic. After 6 years, these blog posts seem to have disappeared.
Good locations for content in docs structure
https://docs.citusdata.com/en/v10.2/develop/api_guc.html#citus-shard-replication-factor-integer
How does this work? (devs)
This feature doesn't work with many Citus features.
Example sql
Corner cases, gotchas
Are there relevant blog posts or outside documentation about the concept/feature?
https://www.citusdata.com/blog/2016/12/15/citus-replication-model-today-and-tomorrow/
Link to relevant commits and regression tests if applicable
https://github.com/citusdata/citus/issues/998