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:45:16 +0100
commit1c400d330934eb6d70982af522f2bc0458eef48d (patch)
tree96beaaf0665b593c83d034fbdfd758366b0fdb6e
parentb7ebda9d8c6f78b3bb31247531d0ef0e64b32a16 (diff)
downloadpostgresql-1c400d330934eb6d70982af522f2bc0458eef48d.tar.gz
postgresql-1c400d330934eb6d70982af522f2bc0458eef48d.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 6744dd6803c..261cedc8d9c 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