database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-24 10:47:04 +03:00
Code

Mention max_prepared_transactions in PREPARE TRANSACTION reference page,

Browse Source 
per Bruce's suggestion.
This commit is contained in:
Tom Lane 2005-08-30 01:37:38 +00:00
parent 13065c7174
commit cc367951a9
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/src/sgml/ref/prepare_transaction.sgml
View File

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