Assorted typo fixes

Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>

From: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
To: pgsql-hackers@postgresql.org
Date: 2023-12-27T21:51:26Z
Lists: pgsql-hackers

Attachments

Hi folks,

I was playing around with the `typos` tool
(https://github.com/crate-ci/typos), and thought I'd run it on the
posgres repo for fun.  After a bit of tweaking to get rid of most false
positives (see separately attached .typos.toml file), it came up with a
useful set of suggestions, some of which I applied verbatim, others
which needed a bit more rewording.

Attached is a series of patches.  The first one are what I consider
obvious, unambiguous fixes to code comments.  The subsequent ones are
fixes for actual code (variable, function, type names) and docs, one
patch per class of typo.  As far as I can tell, none of the code changes
(except the ECPG one, see below) affect anything exported, so this
should not cause any compatibility issues for extensions.

The ECPG change affects the generated C code, but from my reading of the
callers in descriptor.c and ecpg.trailer, any code that would have
caused it to encounter the affected enum value would fail to compile, so
either the case is not possible, or nobody actually uses whatever syntax
is affected (I don't know enough about ECPG to tell without spending far
too much time digging in the code).

- ilmari

Commits

  1. doc: fix typo "vertexes" -> "vertices"

  2. Fix some typos

  3. jsonpath_exec: fix typo "absense" -> "absence"

  4. libpq: fix typo "occurences" -> "occurrences" in tests

  5. gist: fix typo "split(t)ed" -> "split"

  6. tsquery: fix typo "rewrited" -> "rewritten"

  7. Fix typos in comments and in one isolation test.

  8. *** empty log message ***