| From: | "Magnus Hagander" <magnus(at)hagander(dot)net> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "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 06:13:19 |
| Message-ID: | 200710180813200000@1403217259 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 on the commandline?
/Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacky Leng | 2007-10-18 07:26:36 | Re: Why copy_relation_data only use wal when WALarchiving is enabled |
| Previous Message | Jacky Leng | 2007-10-18 06:04:15 | Re: Why copy_relation_data only use wal when WALarchiving is enabled |