Wiki / Configuration Parameters

Sets the maximum number of transactions that can be in the “prepared” state simultaneously (see PREPARE TRANSACTION). Setting this parameter to zero (which is the default) disables the prepared-transaction feature. This parameter can only be set at server start. If you are not planning to use prepared transactions, this parameter should be set to zero to prevent accidental creation of prepared transactions. If you are using prepared transactions, you will probably want max_prepared_transactions to be at least as large as max_connections, so that every session can have a prepared transaction pending. When running a standby server, you must set this parameter to the same or higher value than on the primary server. Otherwise, queries will not be allowed in the standby server.

English manual coverage begins with PostgreSQL 7.4. Source history and runtime observations have their own recorded version boundaries.

boot val

0

category

Resource Usage / Memory

context

postmaster

documented

true

enumvals

Unknown

extra desc

Unknown

lang

en

max val

262143

metadata version

18

min val

0

name

max_prepared_transactions

short desc

Sets the maximum number of simultaneously prepared transactions.

source

pg-settings-source-snapshot

unit

Unknown

vartype

integer