mirror of
https://github.com/postgres/postgres.git
synced 2025-07-18 17:42:25 +03:00
Fix typo in previous commit
This commit is contained in:
@ -194,7 +194,7 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
|
|||||||
after a database crash if there were unwritten changes.
|
after a database crash if there were unwritten changes.
|
||||||
Also, changes to hash indexes are not replicated over streaming or
|
Also, changes to hash indexes are not replicated over streaming or
|
||||||
file-based replication after the initial base backup, so they
|
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.
|
For these reasons, hash index use is presently discouraged.
|
||||||
</para>
|
</para>
|
||||||
</caution>
|
</caution>
|
||||||
|
@ -446,7 +446,7 @@ Indexes:
|
|||||||
after a database crash if there were unwritten changes.
|
after a database crash if there were unwritten changes.
|
||||||
Also, changes to hash indexes are not replicated over streaming or
|
Also, changes to hash indexes are not replicated over streaming or
|
||||||
file-based replication after the initial base backup, so they
|
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.
|
For these reasons, hash index use is presently discouraged.
|
||||||
</para>
|
</para>
|
||||||
</caution>
|
</caution>
|
||||||
|
Reference in New Issue
Block a user