diff options
| -rw-r--r-- | doc/src/sgml/indices.sgml | 2 | ||||
| -rw-r--r-- | 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 <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 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. </para> </caution> |