aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/cluster.c
diff options
context:
space:
mode:
authorGreg Stark <stark@mit.edu>2016-06-03 15:13:36 +0100
committerGreg Stark <stark@mit.edu>2016-06-03 16:08:45 +0100
commite1623c3959aac707732d7a6ad09adfb5751763b3 (patch)
tree3f73cc1c228576ae41f7f2444abb3dc65250c740 /src/backend/commands/cluster.c
parentee4af347ba89b8492d1f86b6456865e1de1d030f (diff)
downloadpostgresql-e1623c3959aac707732d7a6ad09adfb5751763b3.tar.gz
postgresql-e1623c3959aac707732d7a6ad09adfb5751763b3.zip
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
Diffstat (limited to 'src/backend/commands/cluster.c')
-rw-r--r--src/backend/commands/cluster.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c
index 5cb28cfa735..43bbd905919 100644
--- a/src/backend/commands/cluster.c
+++ b/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