We originally anticipated that customers might want to use pg_shard's "simpler" SELECT plans, even within CitusDB, leaving open the possibility (through configuration) that they could opt-in to using CitusDB's more capable (and complex) planner. We now think this behavior is unexpected to CitusDB users, so want to change pg_shard's default (out-of-the-box) behavior to use CitusDB's planner unless the user opts-out.
We originally anticipated that customers might want to use
pg_shard's "simpler"SELECTplans, even within CitusDB, leaving open the possibility (through configuration) that they could opt-in to using CitusDB's more capable (and complex) planner. We now think this behavior is unexpected to CitusDB users, so want to changepg_shard's default (out-of-the-box) behavior to use CitusDB's planner unless the user opts-out.