summaryrefslogtreecommitdiff
path: root/src/backend/commands
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2018-07-09 16:10:44 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2018-07-18 16:17:32 +0300
commit6b387179baab8d0e5da6570678eefbe61f3acc79 (patch)
tree1b9f79c66f804c5d9a6aa0d3c142feefcec95cf3 /src/backend/commands
parent94019c879a138454af723fa8bfc346d4a44ecd47 (diff)
downloadpostgresql-6b387179baab8d0e5da6570678eefbe61f3acc79.tar.gz
Fix misc typos, mostly in comments.
A collection of typos I happened to spot while reading code, as well as grepping for common mistakes. Backpatch to all supported versions, as applicable, to avoid conflicts when backporting other commits in the future.
Diffstat (limited to 'src/backend/commands')
-rw-r--r--src/backend/commands/cluster.c2
-rw-r--r--src/backend/commands/explain.c2
2 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c
index 482d463420..0112a87224 100644
--- a/src/backend/commands/cluster.c
+++ b/src/backend/commands/cluster.c
@@ -1581,7 +1581,7 @@ finish_heap_swap(Oid OIDOldHeap, Oid OIDNewHeap,
* swap_relation_files()), thus relfrozenxid was not updated. That's
* annoying because a potential reason for doing a VACUUM FULL is a
* imminent or actual anti-wraparound shutdown. So, now that we can
- * access the new relation using it's indices, update relfrozenxid.
+ * access the new relation using its indices, update relfrozenxid.
* pg_class doesn't have a toast relation, so we don't need to update the
* corresponding toast relation. Not that there's little point moving all
* relfrozenxid updates here since swap_relation_files() needs to write to
diff --git a/src/backend/commands/explain.c b/src/backend/commands/explain.c
index 73d94b7235..16a80a0ea1 100644
--- a/src/backend/commands/explain.c
+++ b/src/backend/commands/explain.c
@@ -3341,7 +3341,7 @@ ExplainPropertyListNested(const char *qlabel, List *data, ExplainState *es)
* If "numeric" is true, the value is a number (or other value that
* doesn't need quoting in JSON).
*
- * If unit is is non-NULL the text format will display it after the value.
+ * If unit is non-NULL the text format will display it after the value.
*
* This usually should not be invoked directly, but via one of the datatype
* specific routines ExplainPropertyText, ExplainPropertyInteger, etc.