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 16089.1192682142@sss.pgh.pa.us
Whole thread Raw
In response to max_prepared_transactions default ... why 5?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: max_prepared_transactions default ... why 5?
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
> I'm writing up the new GUCs, and noticed that max_prepared_transactions 
> defaults to 5.  This is too many for most applications (which don't use them 
> at all) and far too few for applications which use them regularly.  

I think the intention was to have enough so you could test 'em (in
particular, run the regression tests) without eating resources for
the majority of installations that aren't using them.

Certainly an installation that *is* using 'em would want a higher
setting.
        regards, tom lane


pgsql-hackers by date:

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