aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Riggs <simon@2ndQuadrant.com>2012-10-17 09:19:24 +0100
committerSimon Riggs <simon@2ndQuadrant.com>2012-10-17 09:19:24 +0100
commit4be1d015b8bf1ae43dd7c99fe6039e00b02cfc28 (patch)
tree7f1e070a06ed565032f49d80c0584e240c4a3409
parent679f2ca25b34df013b57eb8aa8b32d6c3f56721a (diff)
downloadpostgresql-4be1d015b8bf1ae43dd7c99fe6039e00b02cfc28.tar.gz
postgresql-4be1d015b8bf1ae43dd7c99fe6039e00b02cfc28.zip
Fix typo in previous commit
-rw-r--r--doc/src/sgml/indices.sgml2
-rw-r--r--doc/src/sgml/ref/create_index.sgml2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml
index 9eb948d6bcc..e6a14de5040 100644
--- a/doc/src/sgml/indices.sgml
+++ b/doc/src/sgml/indices.sgml
@@ -199,7 +199,7 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
after a database crash if there were unwritten changes.
Also, changes to hash indexes are not replicated over streaming or
file-based replication after the initial base backup, so they
- give wrong anwers to queries that subsequently use them.
+ give wrong answers to queries that subsequently use them.
For these reasons, hash index use is presently discouraged.
</para>
</caution>
diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 2403b7642a1..d800701ff4e 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -473,7 +473,7 @@ Indexes:
after a database crash if there were unwritten changes.
Also, changes to hash indexes are not replicated over streaming or
file-based replication after the initial base backup, so they
- give wrong anwers to queries that subsequently use them.
+ give wrong answers to queries that subsequently use them.
For these reasons, hash index use is presently discouraged.
</para>
</caution>