From df35b7e33ef6354ef8530ba9eabcdb2010b0ca39 Mon Sep 17 00:00:00 2001 From: Simon Riggs Date: Wed, 17 Oct 2012 09:21:29 +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 9e090af0a0f..c4abaf894d1 100644 --- a/doc/src/sgml/indices.sgml +++ b/doc/src/sgml/indices.sgml @@ -194,7 +194,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 06bd06ba7c9..701f6513683 100644 --- a/doc/src/sgml/ref/create_index.sgml +++ b/doc/src/sgml/ref/create_index.sgml @@ -446,7 +446,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.39.5