| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Zoltán Böszörményi <zb(at)cybertec(dot)at> |
| Cc: | Hari Babu <haribabu(dot)kommi(at)huawei(dot)com>, 'Craig Ringer' <craig(at)2ndQuadrant(dot)com>, 'Hans-Jürgen Schönig' <hs(at)cybertec(dot)at>, 'Ants Aasma' <ants(at)cybertec(dot)at>, 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 'PostgreSQL Hackers' <pgsql-hackers(at)postgresql(dot)org>, 'Amit kapila' <amit(dot)kapila(at)huawei(dot)com> |
| Subject: | Re: Strange Windows problem, lock_timeout test request |
| Date: | 2013-01-31 14:22:46 |
| Message-ID: | 20130131142246.GA4883@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zoltán Böszörményi wrote:
> I have found a little time to look into this problem and
> found a way to make pg_regress use prepared_xacts_1.out.
> I had to change line 2193 in pg_regress.c from
>
> fputs("max_prepared_transactions = 2\n", pg_conf);
>
> to
>
> fputs("max_prepared_transactions = 0\n", pg_conf);
>
> The patch now passed "make check" in both cases.
That sounds a lot more difficult than just using "make installcheck" and
configure the running server with zero prepared xacts ...
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltán Böszörményi | 2013-01-31 14:55:46 | Re: Strange Windows problem, lock_timeout test request |
| Previous Message | Ali Dar | 2013-01-31 14:02:43 | Re: information schema parameter_default implementation |