Fix various common mispellings.

Mostly these are just comments but there are a few in documentation
and a handful in code and tests. Hopefully this doesn't cause too much
unnecessary pain for backpatching. I relented from some of the most
common like "thru" for that reason. The rest don't seem numerous
enough to cause problems.

Thanks to Kevin Lyda's tool https://pypi.python.org/pypi/misspellings

Author: gsstark

doc/src/sgml/config.sgml

@@ -2518,7 +2518,7 @@ include_dir 'conf.d'
         less than <varname>wal_writer_flush_after</> bytes of WAL have been
         produced since, WAL is only written to the OS, not flushed to disk.
         If <varname>wal_writer_flush_after</> is set to <literal>0</> WAL is
-        flushed everytime the WAL writer has written WAL.  The default is
+        flushed every time the WAL writer has written WAL.  The default is
         <literal>1MB</literal>. This parameter can only be set in the
         <filename>postgresql.conf</> file or on the server command line.
        </para>

doc/src/sgml/pgcrypto.sgml

@@ -866,7 +866,7 @@ Applies to: pgp_sym_encrypt
     be a value between 1024 and 65011712, inclusive.
    </para>
 <literallayout>
-Default: A random value bewteen 65536 and 253952
+Default: A random value between 65536 and 253952
 Applies to: pgp_sym_encrypt, only with s2k-mode=3
 </literallayout>
   </sect4>

doc/src/sgml/ref/psql-ref.sgml

@@ -4168,7 +4168,7 @@ testdb=&gt; <userinput>\crosstabview first second</userinput>
 </programlisting>
 
 This second example shows a multiplication table with rows sorted in reverse
-numerical order and columns with an independant, ascending numerical order.
+numerical order and columns with an independent, ascending numerical order.
 <programlisting>
 testdb=&gt; <userinput>SELECT t1.first as "A", t2.first+100 AS "B", t1.first*(t2.first+100) as "AxB",</userinput>
 testdb(&gt; <userinput>row_number() over(order by t2.first) AS ord</userinput>

src/backend/access/transam/generic_xlog.c

@@ -64,7 +64,7 @@ struct GenericXLogState
 	/*
 	 * page's images. Should be first in this struct to have MAXALIGN'ed
 	 * images addresses, because some code working with pages directly aligns
-	 * addresses, not an offsets from begining of page
+	 * addresses, not offsets from beginning of page
 	 */
 	char		images[MAX_GENERIC_XLOG_PAGES * BLCKSZ];
 	PageData	pages[MAX_GENERIC_XLOG_PAGES];

src/backend/catalog/namespace.c

@@ -297,7 +297,7 @@ RangeVarGetRelidExtended(const RangeVar *relation, LOCKMODE lockmode,
 					namespaceId = LookupExplicitNamespace(relation->schemaname, missing_ok);
 
 					/*
-					 * For missing_ok, allow a non-existant schema name to
+					 * For missing_ok, allow a non-existent schema name to
 					 * return InvalidOid.
 					 */
 					if (namespaceId != myTempNamespace)

src/backend/catalog/sql_features.txt

@@ -316,7 +316,7 @@ F831	Full cursor update			NO
 F831	Full cursor update	01	Updatable scrollable cursors	NO	
 F831	Full cursor update	02	Updatable ordered cursors	NO	
 F841	LIKE_REGEX predicate			NO	
-F842	OCCURENCES_REGEX function			NO	
+F842	OCCURRENCES_REGEX function			NO	
 F843	POSITION_REGEX function			NO	
 F844	SUBSTRING_REGEX function			NO	
 F845	TRANSLATE_REGEX function			NO	

src/backend/commands/cluster.c

@@ -248,7 +248,7 @@ cluster(ClusterStmt *stmt, bool isTopLevel)
  * swapping the relfilenodes of the new table and the old table, so
  * the OID of the original table is preserved.  Thus we do not lose
  * GRANT, inheritance nor references to this table (this was a bug
- * in releases thru 7.3).
+ * in releases through 7.3).
  *
  * Indexes are rebuilt too, via REINDEX. Since we are effectively bulk-loading
  * the new table, it's better to create the indexes afterwards than to fill

src/backend/main/main.c

@@ -179,7 +179,7 @@ main(int argc, char *argv[])
 		 * read-only activities.  The -C case is important because pg_ctl may
 		 * try to invoke it while still holding administrator privileges on
 		 * Windows.  Note that while -C can normally be in any argv position,
-		 * if you wanna bypass the root check you gotta put it first.  This
+		 * if you want to bypass the root check you must put it first.  This
 		 * reduces the risk that we might misinterpret some other mode's -C
 		 * switch as being the postmaster/postgres one.
 		 */

src/backend/nodes/README

@@ -46,7 +46,7 @@ FILES IN src/include/nodes/
 Steps to Add a Node
 -------------------
 
-Suppose you wanna define a node Foo:
+Suppose you want to define a node Foo:
 
 1. Add a tag (T_Foo) to the enum NodeTag in nodes.h.  (If you insert the
    tag in a way that moves the numbers associated with existing tags,

src/backend/optimizer/util/tlist.c

@@ -770,7 +770,7 @@ apply_pathtarget_labeling_to_tlist(List *tlist, PathTarget *target)
  *	  the aggtranstype or aggserialtype. This allows exprType() to return the
  *	  actual type that will be produced.
  *
- * Note: We expect 'target' to be a flat target list and not have Aggrefs burried
+ * Note: We expect 'target' to be a flat target list and not have Aggrefs buried
  * within other expressions.
  */
 void