Skip to content

P
Postgres FD Implementation
Commit d64e81c0 authored by Alvaro Herrera's avatar Alvaro Herrera
Browse files
Options

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

parent ffe8c7c6
Show whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
doc/src/sgml/mvcc.sgml
View file @ d64e81c0
<!-- $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"> <chapter id="mvcc">
<title>Concurrency Control</title> <title>Concurrency Control</title>
...@@ -565,7 +565,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2; ...@@ -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 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 between one lock mode and another is the set of lock modes with
which each conflicts (see <xref linkend="table-lock-compatibility">). 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 modes on the same table at the same time. (However, a transaction
never conflicts with itself. For example, it might acquire never conflicts with itself. For example, it might acquire
<literal>ACCESS EXCLUSIVE</literal> lock and later acquire <literal>ACCESS EXCLUSIVE</literal> lock and later acquire
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment