|
1 | 1 | <!-- |
2 | | -$PostgreSQL: pgsql/doc/src/sgml/ref/prepare_transaction.sgml,v 1.2 2005/08/01 19:38:03 momjian Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/ref/prepare_transaction.sgml,v 1.3 2005/08/30 01:37:38 tgl Exp $ |
3 | 3 | PostgreSQL documentation |
4 | 4 | --> |
5 | 5 |
|
@@ -117,6 +117,16 @@ PREPARE TRANSACTION <replaceable class="PARAMETER">transaction_id</replaceable> |
117 | 117 | committed or rolled back as soon as an external transaction manager |
118 | 118 | has verified that other databases are also prepared to commit. |
119 | 119 | </para> |
| 120 | + |
| 121 | + <para> |
| 122 | + If you make any serious use of prepared transactions, you will probably |
| 123 | + want to increase the value of <xref |
| 124 | + linkend="guc-max-prepared-transactions">, as the default setting is |
| 125 | + quite small (to avoid wasting resources for those who don't use it). |
| 126 | + It is recommendable to make it at least equal to |
| 127 | + <xref linkend="guc-max-connections">, so that every session can have |
| 128 | + a prepared transaction pending. |
| 129 | + </para> |
120 | 130 | </refsect1> |
121 | 131 |
|
122 | 132 | <refsect1 id="sql-prepare-transaction-examples"> |
|