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

From Magnus Hagander
Subject Re: max_prepared_transactions default ... why 5?
Date
Msg-id 200710180813200000@1403217259
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?
Re: max_prepared_transactions default ... why 5?
List pgsql-hackers
> > 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.

Can' we make the default 0, which is what the majority should want, and have the regression test explicitly set it up
onthe commandline?
 

/Magnus



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Release notes introductory text
Next
From: "Jacky Leng"
Date:
Subject: Re: Why copy_relation_data only use wal when WALarchiving is enabled