aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/gist.sgml
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2007-01-31 20:56:20 +0000
committerBruce Momjian <bruce@momjian.us>2007-01-31 20:56:20 +0000
commita134ee33794d7066143f5587d9c36bcca62bfc39 (patch)
tree86772780b602023fbc8f9d7e50fb9d5fa5bd7c3f /doc/src/sgml/gist.sgml
parent67a1ae9f05f9311768ba0a4819f6b09d449c4294 (diff)
downloadpostgresql-a134ee33794d7066143f5587d9c36bcca62bfc39.tar.gz
postgresql-a134ee33794d7066143f5587d9c36bcca62bfc39.zip
Update documentation on may/can/might:
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash". Also update two error messages mentioned in the documenation to match.
Diffstat (limited to 'doc/src/sgml/gist.sgml')
-rw-r--r--doc/src/sgml/gist.sgml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/gist.sgml b/doc/src/sgml/gist.sgml
index 2418c72aa2a..a02da6a9f65 100644
--- a/doc/src/sgml/gist.sgml
+++ b/doc/src/sgml/gist.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.27 2006/10/23 18:10:31 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/gist.sgml,v 1.28 2007/01/31 20:56:17 momjian Exp $ -->
<chapter id="GiST">
<title>GiST Indexes</title>
@@ -248,7 +248,7 @@
Usually, replay of the WAL log is sufficient to restore the integrity
of a GiST index following a database crash. However, there are some
corner cases in which the index state is not fully rebuilt. The index
- will still be functionally correct, but there may be some performance
+ will still be functionally correct, but there might be some performance
degradation. When this occurs, the index can be repaired by
<command>VACUUM</>ing its table, or by rebuilding the index using
<command>REINDEX</>. In some cases a plain <command>VACUUM</> is