Manage
CO.NF for your Blog
Configuration Snippet Parameter Snippet

max_prepared_transactions

  1. Documentation
  2. Resource Usage
  3. Memory
  4. max_prepared_transactions
COPY SHARING LINK
Type: integer
Default: 0
Min: 0
Max: 262143
Context: postmaster
Restart: true
Sets the maximum number of simultaneously prepared transactions

Sets the maximum number of transactions that can be in the prepared state simultaneously (see sql-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.

Official docs

Search in source code

Recommendations

Most applications do not use XA prepared transactions, so should set this parameter to 0. If you do require prepared transactions, you should set this equal to max_connections to avoid blocking. May require increasing kernel memory parameters.
By annotated.conf

Comments