Set default threshold on get_rebalance_table_shards_plan to 0, like rebalance_table_shards (#3039)

In this PR the default `threshold` of `rebalance_table_shards` was set to 0: https://github.com/citusdata/shard_rebalancer/pull/73
However, the default for get_rebalance_table_shards_plan was not updated. This
can cause the confusing situation where the actual steps run by
`rebalance_table_shards` are not the same as the ones returned by
`get_rebalance_table_shards_plan`.
pull/3021/head
Jelte Fennema 2019-09-27 17:21:36 +02:00 committed by GitHub
parent 6adf64efdb
commit dab16be283
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -5,7 +5,7 @@
--
CREATE OR REPLACE FUNCTION pg_catalog.get_rebalance_table_shards_plan(
relation regclass,
threshold float4 default 0.1,
threshold float4 default 0,
max_shard_moves int default 1000000,
excluded_shard_list bigint[] default '{}')
RETURNS TABLE (table_name regclass,

View File

@ -5,7 +5,7 @@
--
CREATE OR REPLACE FUNCTION pg_catalog.get_rebalance_table_shards_plan(
relation regclass,
threshold float4 default 0.1,
threshold float4 default 0,
max_shard_moves int default 1000000,
excluded_shard_list bigint[] default '{}')
RETURNS TABLE (table_name regclass,