diff options
author | Bruce Momjian | 2000-11-04 17:09:24 +0000 |
---|---|---|
committer | Bruce Momjian | 2000-11-04 17:09:24 +0000 |
commit | 6952b3196bb5898c82a6aa5e6292bcf051537f44 (patch) | |
tree | a428b91f83dd3acd4695ceaf9fa3434feafd1df6 /doc/src | |
parent | b61f681f2323729eda5e22f97010528f41adae1b (diff) |
Update FAQ_DEV.
Diffstat (limited to 'doc/src')
-rw-r--r-- | doc/src/FAQ/FAQ_DEV.html | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index ba60c157c21..4da26a9d3a2 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -38,6 +38,7 @@ tables from the backend code?<BR> <a href="#10">10</a>) What is elog()?<BR> <a href="#11">11</a>) What is configure all about?<BR> <a href="#12">12</a>) How do I add a new port?<BR> +<a href="#13">13</a>) What is CommandCounterIncrement()?<BR> <BR> <HR> @@ -481,6 +482,18 @@ 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> + +Normally, transactions can not see the rows they modify. This allows <CODE> +UPDATE foo SET x = x + 1</CODE> to work correctly. +<P> + +However, there are cases where a transactions needs to see rows affected +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> </BODY> </HTML> |