Re: max_prepared_transactions default ... why 5?

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: max_prepared_transactions default ... why 5?
Date: 2007-10-18 13:13:48
Message-ID: 20071018131348.GP5031@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Magnus Hagander (magnus(at)hagander(dot)net) wrote:
> > 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 on the commandline?

I'm with Magnus on this one. Having it set to "just enough to test
with" is just plain terrible. A value of '5' seems high enough that it
might be fine while on a development system and maybe for a short time
on a production system which means it might not get noticed early enough
to get picked up on and fixed by an admin before a user notices.

I also like the on/off option, with the default being 'off' (where that
really means *off*, not "on, but with a small number"- that would be
even worse than the current situation).

Thanks,

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Boergesson, Cheryl 2007-10-18 13:23:53 upgrade from 8.0.3 to 8.1.10 crash
Previous Message Pavel Stehule 2007-10-18 12:45:33 Re: Proposal: generate_iterator functions