aboutsummaryrefslogtreecommitdiff
path: root/doc/src/FAQ/FAQ_DEV.html
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2000-11-04 18:23:36 +0000
committerBruce Momjian <bruce@momjian.us>2000-11-04 18:23:36 +0000
commitaf171286560a00b6f91f9aad8999d9d757098614 (patch)
tree10eb06e35444f2212dbcad22f512c9477a66ff07 /doc/src/FAQ/FAQ_DEV.html
parent6952b3196bb5898c82a6aa5e6292bcf051537f44 (diff)
downloadpostgresql-af171286560a00b6f91f9aad8999d9d757098614.tar.gz
postgresql-af171286560a00b6f91f9aad8999d9d757098614.zip
Update FAQ_DEV.
Diffstat (limited to 'doc/src/FAQ/FAQ_DEV.html')
-rw-r--r--doc/src/FAQ/FAQ_DEV.html4
1 files changed, 2 insertions, 2 deletions
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 <I>backend/port</I> directory if you need special files for
your OS.<P>
-<H3><a name="13">13</a>) What is CommandCounterIncrement()?</H3><P>
+<H3><a name="13">13</a>) What is CommandCounterIncrement()?</H3><P>
Normally, transactions can not see the rows they modify. This allows <CODE>
UPDATE foo SET x = x + 1</CODE> 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. <I>CommandCounterIncrement()</I> increments the Command
-Counter, creating a new piece of the transaction. <P>
+Counter, creating a new part of the transaction. <P>
</BODY>
</HTML>