summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2019-09-20 08:05:54 +0530
committerAmit Kapila <akapila@postgresql.org>2019-09-20 08:22:13 +0530
commit6133c59e17f98420a30197428f881f469c113f32 (patch)
treed5d5831022b21c63e53eef25137a09ebfbbfec56
parent388939748a7683b1e703de8d11ead60b0be3edc7 (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 08bdf7c4252..0c2d008b86c 100644
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -811,7 +811,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