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:55:47 +0530
commit2a98eefc1a15dc32e816ced86d1fd768fefb54b0 (patch)
treea612c65e6d7037c2fac89fae665fd51d3e3b4199
parent984b9ba1d119ee59babea515b2ecab70b7b11910 (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 4e8d3a378e0..f8b8ab40b68 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