From: Simon Riggs Date: Wed, 17 Oct 2012 08:19:24 +0000 (+0100) Subject: Fix typo in previous commit X-Git-Tag: REL9_2_2~70 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=4be1d015b8bf1ae43dd7c99fe6039e00b02cfc28;p=postgresql Fix typo in previous commit --- diff --git a/doc/src/sgml/indices.sgml b/doc/src/sgml/indices.sgml index 9eb948d6bc..e6a14de504 100644 --- a/doc/src/sgml/indices.sgml +++ b/doc/src/sgml/indices.sgml @@ -199,7 +199,7 @@ CREATE INDEX name ON table 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. diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml index 2403b7642a..d800701ff4 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.