Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Paquier2020-06-12 12:05:10 +0000
committerMichael Paquier2020-06-12 12:05:10 +0000
commitaaf8c990502f7bb28c10f6bab1d23fe2f9f0b537 (patch)
treedfc9670fce438cb3fea0eefe98532facdf254ed0 /src/backend
parentffd2582297b86f640b60ba46097b70743f920d35 (diff)
Fix typos and some format mistakes in comments
Author: Justin Pryzby Discussion: https://postgr.es/m/20200612023709.GC14879@telsasoft.com
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/replication/logical/origin.c2
-rw-r--r--src/backend/replication/logical/relation.c2
-rw-r--r--src/backend/utils/mmgr/README2
3 files changed, 3 insertions, 3 deletions
diff --git a/src/backend/replication/logical/origin.c b/src/backend/replication/logical/origin.c
index 1ca4479605c..dec9e951195 100644
--- a/src/backend/replication/logical/origin.c
+++ b/src/backend/replication/logical/origin.c
@@ -427,7 +427,7 @@ restart:
/*
- * Lookup replication origin via it's oid and return the name.
+ * Lookup replication origin via its oid and return the name.
*
* The external name is palloc'd in the calling context.
*
diff --git a/src/backend/replication/logical/relation.c b/src/backend/replication/logical/relation.c
index 5781b42af62..a60c73d74d5 100644
--- a/src/backend/replication/logical/relation.c
+++ b/src/backend/replication/logical/relation.c
@@ -576,7 +576,7 @@ logicalrep_partmap_init(void)
* the attribute map, which can be different for the partition.
*
* Note there's no logicalrep_partition_close, because the caller closes the
- * the component relation.
+ * component relation.
*/
LogicalRepRelMapEntry *
logicalrep_partition_open(LogicalRepRelMapEntry *root,
diff --git a/src/backend/utils/mmgr/README b/src/backend/utils/mmgr/README
index e892779cddf..221b4bd3433 100644
--- a/src/backend/utils/mmgr/README
+++ b/src/backend/utils/mmgr/README
@@ -462,7 +462,7 @@ Memory Accounting
-----------------
One of the basic memory context operations is determining the amount of
-memory used in the context (and it's children). We have multiple places
+memory used in the context (and its children). We have multiple places
that implement their own ad hoc memory accounting, and this is meant to
provide a unified approach. Ad hoc accounting solutions work for places
with tight control over the allocations or when it's easy to determine