From e07633646a22734e85d7fc58a66855f747128e6b Mon Sep 17 00:00:00 2001 From: Andres Freund Date: Sun, 14 Jun 2020 14:22:47 -0700 Subject: code: replace 'master' with 'leader' where appropriate. Leader already is the more widely used terminology, but a few places didn't get the message. Author: Andres Freund Reviewed-By: David Steele Discussion: https://postgr.es/m/20200615182235.x7lch5n6kcjq4aue@alap3.anarazel.de --- src/backend/executor/execGrouping.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/executor/execGrouping.c') diff --git a/src/backend/executor/execGrouping.c b/src/backend/executor/execGrouping.c index 8be36ca7634..019b87df21e 100644 --- a/src/backend/executor/execGrouping.c +++ b/src/backend/executor/execGrouping.c @@ -190,7 +190,7 @@ BuildTupleHashTableExt(PlanState *parent, hashtable->cur_eq_func = NULL; /* - * If parallelism is in use, even if the master backend is performing the + * If parallelism is in use, even if the leader backend is performing the * scan itself, we don't want to create the hashtable exactly the same way * in all workers. As hashtables are iterated over in keyspace-order, * doing so in all processes in the same way is likely to lead to -- cgit v1.2.3