docs: adjust tag indenting and add MERGE mention

Discussion: https://postgr.es/m/CAMpnoC4_WsY3gsY+ud-Z0GDbafR=K7t7cXn2gatEqFnsRNY3yQ@mail.gmail.com

Author: Will Mortensen

diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml
index b87ad5cc53831cf1be7c70ed8b698cb377b568fc..0adc457f03a0b7b272ae4ff959b5713acecc884a 100644 (file)
--- a/doc/src/sgml/mvcc.sgml
+++ b/doc/src/sgml/mvcc.sgml
@@ -109,8 +109,8 @@
        dirty read
        dirty read
       
-     
-      
+      
+       
         A transaction reads data written by a concurrent uncommitted transaction.
        
       
@@ -121,8 +121,8 @@
        nonrepeatable read
        nonrepeatable read
       
-     
-      
+      
+       
         A transaction re-reads data it has previously read and finds that data
         has been modified by another transaction (that committed since the
         initial read).
@@ -135,8 +135,8 @@
        phantom read
        phantom read
       
-     
-      
+      
+       
         A transaction re-executes a query returning a set of rows that satisfy a
         search condition and finds that the set of rows satisfying the condition
         has changed due to another recently-committed transaction.
@@ -149,8 +149,8 @@
        serialization anomaly
        serialization anomaly
       
-     
-      
+      
+       
         The result of successfully committing a group of transactions
         is inconsistent with all possible orderings of running those
         transactions one at a time.
@@ -1752,9 +1752,9 @@ SELECT pg_advisory_lock(q.id) FROM
      changes in the table.  A repeatable read transaction's snapshot is actually
      frozen at the start of its first query or data-modification command
      (SELECT, INSERT,
-     UPDATE, or DELETE), so
-     it is possible to obtain locks explicitly before the snapshot is
-     frozen.
+     UPDATE, DELETE, or
+     MERGE), so it is possible to obtain locks explicitly
+     before the snapshot is frozen.