Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitd64e81c

Browse files
committed
Remove spurious dot, per bug #5446 reported by koizumistr@minos.ocn.ne.jp
1 parentffe8c7c commitd64e81c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎doc/src/sgml/mvcc.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.74 2010/04/0307:22:55 petere Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/mvcc.sgml,v 2.75 2010/05/0315:35:30 alvherre Exp $ -->
22

33
<chapter id="mvcc">
44
<title>Concurrency Control</title>
@@ -565,7 +565,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2;
565565
mode &mdash; but the semantics are all the same. The only real difference
566566
between one lock mode and another is the set of lock modes with
567567
which each conflicts (see <xref linkend="table-lock-compatibility">).
568-
. Two transactions cannot hold locks of conflicting
568+
Two transactions cannot hold locks of conflicting
569569
modes on the same table at the same time. (However, a transaction
570570
never conflicts with itself. For example, it might acquire
571571
<literal>ACCESS EXCLUSIVE</literal> lock and later acquire

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp