| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | jd(at)commandprompt(dot)com, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Prepared transactions vs novice DBAs, again |
| Date: | 2009-04-22 18:37:16 |
| Message-ID: | 49EF63DC.6040108@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
>
> I think we should change the way we test it. Could we simply make
> max_prepared_transactions = 0 the default, but put
> "max_prepared_transactions = 5" into the config file in "make check"?
> That seems like the best alternative, it doesn't seem right to build
> extra config options or other infrastructure into the server just so
> that the regression tests can test a feature.
>
>
FWIW, modern versions of the buildfarm script have support for
non-standard options in the install-check pieces.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-04-22 18:40:56 | Re: Prepared transactions vs novice DBAs, again |
| Previous Message | Tom Lane | 2009-04-22 18:35:22 | Re: trouble with to_char('L') |