This commit does the followings:
- Refactor reference table replication logic for replicating to a
single node instead of always replicating to all nodes
- Add a new parameter to master_add_node(..,.., activate_node
DEFAULT true)
- If activate is true, replicate reference tables
- Else, do not replicate reference tables
- New API for activating node: master_activate_node(host, port)
- currently only replicates reference tables
This adds a replication_model GUC which is used as the replication
model for any new distributed table that is not a reference table.
With this change, tables with replication factor 1 are no longer
implicitly MX tables.
The GUC is similarly respected during empty shard creation for e.g.
existing append-partitioned tables. If the model is set to streaming
while replication factor is greater than one, table and shard creation
routines will error until this invalid combination is corrected.
Changing this parameter requires superuser permissions.
In tests related to automatic reference table creation and deletion, there were some
tests whose output may change order thus creating inconsistent test results. With this
change we add ORDER BY clause to related tests to have consistent output.
Since we will now replicate reference tables each time we add node, we need to ensure
that test space is clean in terms of reference tables before any add node operation.
For this purpose we had to change order of multi_drop_extension test which caused
change of some of the colocation ids.
With this change we introduce new UDF, upgrade_to_reference_table, which can be used to
upgrade existing broadcast tables reference tables. For upgrading, we require that given
table contains only one shard.
Önder Kalacı
Jason Petersen
Eren Basak
Burak Yucesoy