diff options
| author | Itagaki Takahiro <itagaki.takahiro@gmail.com> | 2011-02-10 10:58:18 +0900 |
|---|---|---|
| committer | Itagaki Takahiro <itagaki.takahiro@gmail.com> | 2011-02-10 10:58:18 +0900 |
| commit | 5478f991c9f73066d27d75b31876f9977af61db5 (patch) | |
| tree | aca13f31d0263a7889fb2bcaf909797580146b4f | |
| parent | caddcb8f4b96ce48b612e7c987ecde654d624616 (diff) | |
| download | postgresql-5478f991c9f73066d27d75b31876f9977af61db5.tar.gz postgresql-5478f991c9f73066d27d75b31876f9977af61db5.zip | |
Fix typo in the documentation.
by Kevin Grittner
| -rw-r--r-- | doc/src/sgml/mvcc.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index c5d33091001..f42bb091c13 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -604,7 +604,7 @@ ERROR: could not serialize access due to read/write dependencies among transact Consistent use of Serializable transactions can simplify development. The guarantee that any set of concurrent serializable transactions will have the same effect as if they were run one at a time means that if - you can demonstrate that a singe transaction, as written, will do the + you can demonstrate that a single transaction, as written, will do the right thing when run by itself, you can have confidence that it will do the right thing in any mix of serializable transactions, even without any information about what those other transactions might do. It is |