|
109 | 109 | dirty read |
110 | 110 | <indexterm><primary>dirty read</primary></indexterm> |
111 | 111 | </term> |
112 | | - <listitem> |
113 | | - <para> |
| 112 | + <listitem> |
| 113 | + <para> |
114 | 114 | A transaction reads data written by a concurrent uncommitted transaction. |
115 | 115 | </para> |
116 | 116 | </listitem> |
|
121 | 121 | nonrepeatable read |
122 | 122 | <indexterm><primary>nonrepeatable read</primary></indexterm> |
123 | 123 | </term> |
124 | | - <listitem> |
125 | | - <para> |
| 124 | + <listitem> |
| 125 | + <para> |
126 | 126 | A transaction re-reads data it has previously read and finds that data |
127 | 127 | has been modified by another transaction (that committed since the |
128 | 128 | initial read). |
|
135 | 135 | phantom read |
136 | 136 | <indexterm><primary>phantom read</primary></indexterm> |
137 | 137 | </term> |
138 | | - <listitem> |
139 | | - <para> |
| 138 | + <listitem> |
| 139 | + <para> |
140 | 140 | A transaction re-executes a query returning a set of rows that satisfy a |
141 | 141 | search condition and finds that the set of rows satisfying the condition |
142 | 142 | has changed due to another recently-committed transaction. |
|
149 | 149 | serialization anomaly |
150 | 150 | <indexterm><primary>serialization anomaly</primary></indexterm> |
151 | 151 | </term> |
152 | | - <listitem> |
153 | | - <para> |
| 152 | + <listitem> |
| 153 | + <para> |
154 | 154 | The result of successfully committing a group of transactions |
155 | 155 | is inconsistent with all possible orderings of running those |
156 | 156 | transactions one at a time. |
@@ -1752,9 +1752,9 @@ SELECT pg_advisory_lock(q.id) FROM |
1752 | 1752 | changes in the table. A repeatable read transaction's snapshot is actually |
1753 | 1753 | frozen at the start of its first query or data-modification command |
1754 | 1754 | (<literal>SELECT</literal>, <literal>INSERT</literal>, |
1755 | | - <literal>UPDATE</literal>, or <literal>DELETE</literal>), so |
1756 | | - it is possible to obtain locks explicitly before the snapshot is |
1757 | | - frozen. |
| 1755 | + <literal>UPDATE</literal>, <literal>DELETE</literal>, or |
| 1756 | + <literal>MERGE</literal>), so it is possible to obtain locks explicitly |
| 1757 | + before the snapshot is frozen. |
1758 | 1758 | </para> |
1759 | 1759 | </sect2> |
1760 | 1760 | </sect1> |
|
0 commit comments