aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2011-01-11 10:45:16 +0100
committerMagnus Hagander <magnus@hagander.net>2011-01-11 10:46:08 +0100
commita1ed4cf6ca6ee2115d9f618ed7930a97842042a8 (patch)
tree4e185139982d8dfd893fbd3af630ff41d9e94d16
parent628a6b75645d790579ec565f29f94484e92d52bf (diff)
downloadpostgresql-a1ed4cf6ca6ee2115d9f618ed7930a97842042a8.tar.gz
postgresql-a1ed4cf6ca6ee2115d9f618ed7930a97842042a8.zip
Typo fix
Josh Kupershmidt
-rw-r--r--doc/src/sgml/ref/prepare_transaction.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/ref/prepare_transaction.sgml b/doc/src/sgml/ref/prepare_transaction.sgml
index 9792bedcb5d..69c14078c26 100644
--- a/doc/src/sgml/ref/prepare_transaction.sgml
+++ b/doc/src/sgml/ref/prepare_transaction.sgml
@@ -84,7 +84,7 @@ PREPARE TRANSACTION <replaceable class="PARAMETER">transaction_id</replaceable>
<para>
<command>PREPARE TRANSACTION</> is not intended for use in applications
- or interactive sessions. It's purpose is to allow an external
+ or interactive sessions. Its purpose is to allow an external
transaction manager to perform atomic global transactions across multiple
databases or other transactional resources. Unless you're writing a
transaction manager, you probably shouldn't be using <command>PREPARE