saves nearly 700kB in the default shared memory segment size, which seems
worthwhile, and it is a feature that many users won't use anyway. Per
Heikki's argument, there is no point in a compromise value --- those who
are using 2PC at all will probably want it at least equal to max_connections.
But we can't set it to zero by default without breaking the prepared_xacts
regression test.
endterm="sql-prepare-transaction-title">).
Setting this parameter to zero disables the prepared-transaction
feature.
- The default is 50.
+ The default is 5.
This option can only be set at server start.
</para>
#define TWOPHASE_DIR "pg_twophase"
/* GUC variable, can't be changed after startup */
-int max_prepared_xacts = 50;
+int max_prepared_xacts = 5;
/*
* This struct describes one global transaction that is in prepared state
NULL
},
&max_prepared_xacts,
- 50, 0, INT_MAX, NULL, NULL
+ 5, 0, INT_MAX, NULL, NULL
},
#ifdef LOCK_DEBUG
#shared_buffers = 1000 # min 16 or max_connections*2, 8KB each
#temp_buffers = 1000 # min 100, 8KB each
-#max_prepared_transactions = 50 # can be 0 or more
+#max_prepared_transactions = 5 # can be 0 or more
#work_mem = 1024 # min 64, size in KB
#maintenance_work_mem = 16384 # min 1024, size in KB
#max_stack_depth = 2048 # min 100, size in KB