rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove spurious dot, per bug #5446 reported by koizumistr@minos.ocn.ne.jp

This commit is contained in:
Alvaro Herrera 2010-05-03 15:35:30 +00:00
parent ffe8c7c677
commit d64e81c07e
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/mvcc.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.74 2010/04/03 07:22:55 petere Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.75 2010/05/03 15:35:30 alvherre Exp $ -->
<chapter id="mvcc">
<title>Concurrency Control</title>
@ -565,7 +565,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
mode &mdash; but the semantics are all the same. The only real difference
between one lock mode and another is the set of lock modes with
which each conflicts (see <xref linkend="table-lock-compatibility">).
. Two transactions cannot hold locks of conflicting
Two transactions cannot hold locks of conflicting
modes on the same table at the same time. (However, a transaction
never conflicts with itself. For example, it might acquire
<literal>ACCESS EXCLUSIVE</literal> lock and later acquire