Skip site navigation (1) Skip section navigation (2)

pgsql: Change the default value of max_prepared_transactions to zero,

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Change the default value of max_prepared_transactions to zero,
Date: 2009-04-23 00:23:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
Change the default value of max_prepared_transactions to zero, and add
documentation warnings against setting it nonzero unless active use of
prepared transactions is intended and a suitable transaction manager has been
installed.  This should help to prevent the type of scenario we've seen
several times now where a prepared transaction is forgotten and eventually
causes severe maintenance problems (or even anti-wraparound shutdown).

The only real reason we had the default be nonzero in the first place was to
support regression testing of the feature.  To still be able to do that,
tweak pg_regress to force a nonzero value during "make check".  Since we
cannot force a nonzero value in "make installcheck", add a variant regression
test "expected" file that shows the results that will be obtained when
max_prepared_transactions is zero.

Also, extend the HINT messages for transaction wraparound warnings to mention
the possibility that old prepared transactions are causing the problem.

All per today's discussion.

Modified Files:
        config.sgml (r1.214 -> r1.215)
        prepare_transaction.sgml (r1.8 -> r1.9)
        twophase.c (r1.51 -> r1.52)
        varsup.c (r1.83 -> r1.84)
        guc.c (r1.502 -> r1.503)
        postgresql.conf.sample (r1.259 -> r1.260)
        prepared_xacts.out (r1.6 -> r1.7)
        pg_regress.c (r1.61 -> r1.62)
        prepared_xacts.sql (r1.2 -> r1.3)

Added Files:
        prepared_xacts_1.out (r1.1)

pgsql-committers by date

Next:From: User ItagakiDate: 2009-04-23 06:37:30
Subject: reorg - pg_reorg: Fix compile errors on Linux.
Previous:From: Heikki LinnakangasDate: 2009-04-22 19:51:12
Subject: pgsql: After archive recovery, mark the last WAL segment from the parent

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group