Add missing file; new docs for start_transaction.

diff --git a/doc/src/sgml/ref/start_transaction.sgml b/doc/src/sgml/ref/start_transaction.sgml
new file mode 100644 (file)
index 0000000..675b317
--- /dev/null
+++ b/doc/src/sgml/ref/start_transaction.sgml
@@ -0,0 +1,137 @@
+
+
+ 
+  2002-07-26
+ 
+
+ 
+  START TRANSACTION
+  SQL - Language Statements
+ 
+
+ 
+  START TRANSACTION
+  start a transaction block
+ 
+
+ 
+  
+START TRANSACTION [ ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE } ]
+  
+
+  
+   
+    1998-09-27
+   
+   </div>
<div class="diff add">+    Inputs</div>
<div class="diff add">+   
+
+   
+    None.
+   
+  
+
+  
+   
+    1998-09-27
+   
+   </div>
<div class="diff add">+    Outputs</div>
<div class="diff add">+   
+
+   
+
+    
+     
+      
+START TRANSACTION
+       
+      
+       
+    Message returned if successful.
+       
+      
+     
+     
+      
+WARNING:  BEGIN: already a transaction in progress
+       
+      
+       
+    If there is already a transaction in progress when the
+    command is issued.
+       
+      
+     
+    
+   
+  
+ 
+
+ 
+  Description
+
+  
+   This command begins a new transaction. If the isolation level is
+   specified, the new transaction has that isolation level. In all other
+   respects, the behavior of this command is identical to the
+   BEGIN.
+  
+
+ 
+
+ 
+  Notes
+
+  
+   The isolation level of a transaction can also be set with the 
+   linkend="sql-set-transaction" endterm="sql-set-transaction-title">.
+   If no isolation level is specified, the level defaults to
+   READ COMMITTED.
+  
+ 
+
+ 
+  Compatibility
+
+  
+   SQL99
+
+   
+    SERIALIZABLE is the default level in
+    SQL. PostgreSQL
+    does not provide the isolation levels READ UNCOMMITTED
+    and REPEATABLE READ. Because of multiversion
+    concurrency control, the SERIALIZABLE level is
+    not truly serializable. See the User's Guide
+    for details.
+   
+
+   
+    In SQL99 this statement can specify two other
+    properties of the new transaction: whether the transaction is
+    read-only and the size of the diagnostics area. Neither of these
+    concepts are currently supported in
+    PostgreSQL.
+   
+  
+ 
+
+
+