aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon Riggs <simon@2ndQuadrant.com>2012-10-17 09:20:42 +0100
committerSimon Riggs <simon@2ndQuadrant.com>2012-10-17 09:20:42 +0100
commitf34d1fa0c8bd587a165234e0971bba8dc5e1fd2a (patch)
treef78dcd13016ce7c35609e6979c00e6c8f618215e
parent3877b1fa17fc9003691d890cec5557c64db05462 (diff)
downloadpostgresql-f34d1fa0c8bd587a165234e0971bba8dc5e1fd2a.tar.gz
postgresql-f34d1fa0c8bd587a165234e0971bba8dc5e1fd2a.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 c7c3211f1f1..fa479e6ab83 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 8f266ed6d00..8a59a9fd82e 100644
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -458,7 +458,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>