diff options
author | Michael Paquier | 2021-04-09 04:53:07 +0000 |
---|---|---|
committer | Michael Paquier | 2021-04-09 04:53:07 +0000 |
commit | 609b0652af00374b89411ea2613fd5bb92bca92c (patch) | |
tree | f21a820ed35b1ce3c67f2a9da1b5618f805ecea2 /src/backend | |
parent | 796092fb84c08162ae803e83a13aa8bd6d9b23d0 (diff) |
Fix typos and grammar in documentation and code comments
Comment fixes are applied on HEAD, and documentation improvements are
applied on back-branches where needed.
Author: Justin Pryzby
Discussion: https://postgr.es/m/20210408164008.GJ6592@telsasoft.com
Backpatch-through: 9.6
Diffstat (limited to 'src/backend')
-rw-r--r-- | src/backend/catalog/heap.c | 1 | ||||
-rw-r--r-- | src/backend/commands/analyze.c | 2 | ||||
-rw-r--r-- | src/backend/commands/cluster.c | 2 | ||||
-rw-r--r-- | src/backend/commands/copyfrom.c | 2 | ||||
-rw-r--r-- | src/backend/statistics/extended_stats.c | 2 | ||||
-rw-r--r-- | src/backend/utils/adt/jsonfuncs.c | 4 |
6 files changed, 7 insertions, 6 deletions
diff --git a/src/backend/catalog/heap.c b/src/backend/catalog/heap.c index 9f6303266f9..ba03e8aa8f3 100644 --- a/src/backend/catalog/heap.c +++ b/src/backend/catalog/heap.c @@ -1119,6 +1119,7 @@ AddNewRelationType(const char *typeName, * reltypeid: OID to assign to rel's rowtype, or InvalidOid to select one * reloftypeid: if a typed table, OID of underlying type; else InvalidOid * ownerid: OID of new rel's owner + * accessmtd: OID of new rel's access method * tupdesc: tuple descriptor (source of column definitions) * cooked_constraints: list of precooked check constraints and defaults * relkind: relkind for new rel diff --git a/src/backend/commands/analyze.c b/src/backend/commands/analyze.c index 5bdaceefd5d..182a1330332 100644 --- a/src/backend/commands/analyze.c +++ b/src/backend/commands/analyze.c @@ -617,7 +617,7 @@ do_analyze_rel(Relation onerel, VacuumParams *params, * * We assume that VACUUM hasn't set pg_class.reltuples already, even * during a VACUUM ANALYZE. Although VACUUM often updates pg_class, - * exceptions exists. A "VACUUM (ANALYZE, INDEX_CLEANUP OFF)" command + * exceptions exist. A "VACUUM (ANALYZE, INDEX_CLEANUP OFF)" command * will never update pg_class entries for index relations. It's also * possible that an individual index's pg_class entry won't be updated * during VACUUM if the index AM returns NULL from its amvacuumcleanup() diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c index 096a06f7b3b..6487a9e3fcb 100644 --- a/src/backend/commands/cluster.c +++ b/src/backend/commands/cluster.c @@ -1422,7 +1422,7 @@ finish_heap_swap(Oid OIDOldHeap, Oid OIDNewHeap, PROGRESS_CLUSTER_PHASE_FINAL_CLEANUP); /* - * If the relation being rebuild is pg_class, swap_relation_files() + * If the relation being rebuilt is pg_class, swap_relation_files() * couldn't update pg_class's own pg_class entry (check comments in * swap_relation_files()), thus relfrozenxid was not updated. That's * annoying because a potential reason for doing a VACUUM FULL is a diff --git a/src/backend/commands/copyfrom.c b/src/backend/commands/copyfrom.c index 20e7d57d41f..40a54ad0bd7 100644 --- a/src/backend/commands/copyfrom.c +++ b/src/backend/commands/copyfrom.c @@ -410,7 +410,7 @@ CopyMultiInsertBufferCleanup(CopyMultiInsertInfo *miinfo, * Once flushed we also trim the tracked buffers list down to size by removing * the buffers created earliest first. * - * Callers should pass 'curr_rri' is the ResultRelInfo that's currently being + * Callers should pass 'curr_rri' as the ResultRelInfo that's currently being * used. When cleaning up old buffers we'll never remove the one for * 'curr_rri'. */ diff --git a/src/backend/statistics/extended_stats.c b/src/backend/statistics/extended_stats.c index 463d44a68a4..4674168ff80 100644 --- a/src/backend/statistics/extended_stats.c +++ b/src/backend/statistics/extended_stats.c @@ -254,7 +254,7 @@ BuildRelationExtStatistics(Relation onerel, double totalrows, * that would require additional columns. * * See statext_compute_stattarget for details about how we compute statistics - * target for a statistics objects (from the object target, attribute targets + * target for a statistics object (from the object target, attribute targets * and default statistics target). */ int diff --git a/src/backend/utils/adt/jsonfuncs.c b/src/backend/utils/adt/jsonfuncs.c index 9961d27df47..09fcff67299 100644 --- a/src/backend/utils/adt/jsonfuncs.c +++ b/src/backend/utils/adt/jsonfuncs.c @@ -1651,7 +1651,7 @@ push_null_elements(JsonbParseState **ps, int num) * this path. E.g. the path [a][0][b] with the new value 1 will produce the * structure {a: [{b: 1}]}. * - * Called is responsible to make sure such path does not exist yet. + * Caller is responsible to make sure such path does not exist yet. */ static void push_path(JsonbParseState **st, int level, Datum *path_elems, @@ -4887,7 +4887,7 @@ IteratorConcat(JsonbIterator **it1, JsonbIterator **it2, * than just one last element, this flag will instruct to create the whole * chain of corresponding objects and insert the value. * - * JB_PATH_CONSISTENT_POSITION for an array indicates that the called wants to + * JB_PATH_CONSISTENT_POSITION for an array indicates that the caller wants to * keep values with fixed indices. Indices for existing elements could be * changed (shifted forward) in case if the array is prepended with a new value * and a negative index out of the range, so this behavior will be prevented |