summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2019-09-20 07:38:06 +0530
committerAmit Kapila <akapila@postgresql.org>2019-09-20 07:46:39 +0530
commit09f8106b968e10c7855c0a9fd07dd3520d30e4eb (patch)
treeb5240443351c69d471e3b3e9096bc41e8788f219
parent340536dd489286d0f98878843390d92ddc593be0 (diff)
Fix typo in commit 82fa3ff8672.
Reported-By: Kuntal Ghosh (off-list) Backpatch-through: 9.4, like 82fa3ff8672
-rw-r--r--doc/src/sgml/maintenance.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index aee8ff2dfbe..ec8bdcd7a49 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -828,7 +828,7 @@ analyze threshold = analyze base threshold + analyze scale factor * number of tu
<para>
Autovacuum workers generally don't block other commands. If a process
- attempts to acquire a lock that conficts with the
+ attempts to acquire a lock that conflicts with the
<literal>SHARE UPDATE EXCLUSIVE</literal> lock held by autovacuum, lock
acquisition will interrupt the autovacuum. For conflicting lock modes,
see <xref linkend="table-lock-compatibility"/>. However, if the autovacuum