diff options
| author | Andres Freund <andres@anarazel.de> | 2020-06-14 14:22:47 -0700 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2020-07-08 12:58:32 -0700 |
| commit | e07633646a22734e85d7fc58a66855f747128e6b (patch) | |
| tree | b2de0a718b24574d4cc52a493075013667515a19 /src/backend/access/transam/xact.c | |
| parent | 5e7bbb528638c0f6d585bab107ec7a19e3a39deb (diff) | |
| download | postgresql-e07633646a22734e85d7fc58a66855f747128e6b.tar.gz postgresql-e07633646a22734e85d7fc58a66855f747128e6b.zip | |
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
Diffstat (limited to 'src/backend/access/transam/xact.c')
| -rw-r--r-- | src/backend/access/transam/xact.c | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/src/backend/access/transam/xact.c b/src/backend/access/transam/xact.c index 905dc7d8d3b..b3ee7fa7ea0 100644 --- a/src/backend/access/transam/xact.c +++ b/src/backend/access/transam/xact.c @@ -750,7 +750,7 @@ GetCurrentCommandId(bool used) { /* * Forbid setting currentCommandIdUsed in a parallel worker, because - * we have no provision for communicating this back to the master. We + * we have no provision for communicating this back to the leader. We * could relax this restriction when currentCommandIdUsed was already * true at the start of the parallel operation. */ @@ -987,7 +987,7 @@ ExitParallelMode(void) /* * IsInParallelMode * - * Are we in a parallel operation, as either the master or a worker? Check + * Are we in a parallel operation, as either the leader or a worker? Check * this to prohibit operations that change backend-local state expected to * match across all workers. Mere caches usually don't require such a * restriction. State modified in a strict push/pop fashion, such as the @@ -2164,13 +2164,13 @@ CommitTransaction(void) else { /* - * We must not mark our XID committed; the parallel master is + * We must not mark our XID committed; the parallel leader is * responsible for that. */ latestXid = InvalidTransactionId; /* - * Make sure the master will know about any WAL we wrote before it + * Make sure the leader will know about any WAL we wrote before it * commits. */ ParallelWorkerReportLastRecEnd(XactLastRecEnd); @@ -2699,7 +2699,7 @@ AbortTransaction(void) latestXid = InvalidTransactionId; /* - * Since the parallel master won't get our value of XactLastRecEnd in + * Since the parallel leader won't get our value of XactLastRecEnd in * this case, we nudge WAL-writer ourselves in this case. See related * comments in RecordTransactionAbort for why this matters. */ @@ -4488,7 +4488,7 @@ RollbackAndReleaseCurrentSubTransaction(void) /* * Unlike ReleaseCurrentSubTransaction(), this is nominally permitted - * during parallel operations. That's because we may be in the master, + * during parallel operations. That's because we may be in the leader, * recovering from an error thrown while we were in parallel mode. We * won't reach here in a worker, because BeginInternalSubTransaction() * will have failed. |