From f862a326efa3087440bc86cbfe58ea11c977068a Mon Sep 17 00:00:00 2001 From: Simon Riggs Date: Wed, 17 Oct 2012 10:29:30 +0100 Subject: [PATCH] Fix typo in previous commit --- doc/src/sgml/indices.sgml | 2 +- doc/src/sgml/ref/create_index.sgml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) 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. -- 2.40.0