Re: max_prepared_transactions default ... why 5? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: max_prepared_transactions default ... why 5?
Date
Msg-id 16349.1192683634@sss.pgh.pa.us
Whole thread Raw
In response to Re: max_prepared_transactions default ... why 5?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> Yeah, given the amount of memory per xact, I guess we can't actually set the 
> default higher.  I just hate to see a setting that is liable to bite someone 
> on the tuchas so easily.

I seem to recall thinking about replacing the setting with a
"prepared_transactions = on/off" boolean parameter, where "off" could be
defined as still allowing enough to run the regression tests.  The
problem is to choose the "on" setting --- it's not too hard to think of
application behaviors where you need *more* than max_connections
entries.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: max_prepared_transactions default ... why 5?
Next
From: Bruce Momjian
Date:
Subject: Re: max_prepared_transactions default ... why 5?