From af171286560a00b6f91f9aad8999d9d757098614 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sat, 4 Nov 2000 18:23:36 +0000 Subject: Update FAQ_DEV. --- doc/src/FAQ/FAQ_DEV.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 4da26a9d3a2..e62d0c3533a 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -482,7 +482,7 @@ appropriate values. Hopefully, there is already locking code in There is a backend/port directory if you need special files for your OS.

-

13) What is CommandCounterIncrement()?

+

13) What is CommandCounterIncrement()?

Normally, transactions can not see the rows they modify. This allows UPDATE foo SET x = x + 1 to work correctly. @@ -493,7 +493,7 @@ in previous parts of the transaction. This is accomplished using a Command Counter. Incrementing the counter allows transactions to be broken into pieces so each piece can see rows modified by previous pieces. CommandCounterIncrement() increments the Command -Counter, creating a new piece of the transaction.

+Counter, creating a new part of the transaction.

-- cgit v1.2.3