Vik Reykja <vikrey...@gmail.com> wrote:
> in Section 13.2.3 of the 9.1 docs [1], the follow sentence
> fragment can be found:
>
> "using Serializable transactions will allow one transaction to
> commit and and will roll the other back"
>
> Note the double "and" towards the end. (Is this the right list for
> this kind of report?)
When it's strictly documentation and doesn't involve questions of
how the software works, pgsql-docs is probably better, but this
works.
Trivial patch attached. Thanks!
-Kevin
*** a/doc/src/sgml/mvcc.sgml
--- b/doc/src/sgml/mvcc.sgml
***************
*** 547,553 **** SELECT SUM(value) FROM mytab WHERE class = 2;
If either transaction were running at the Repeatable Read isolation level,
both would be allowed to commit; but since there is no serial order of
execution
consistent with the result, using Serializable transactions will allow one
! transaction to commit and and will roll the other back with this message:
<screen>
ERROR: could not serialize access due to read/write dependencies among
transactions
--- 547,553 ----
If either transaction were running at the Repeatable Read isolation level,
both would be allowed to commit; but since there is no serial order of
execution
consistent with the result, using Serializable transactions will allow one
! transaction to commit and will roll the other back with this message:
<screen>
ERROR: could not serialize access due to read/write dependencies among
transactions
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
