Re: Strange Windows problem, lock_timeout test request - Mailing list pgsql-hackers

From Zoltán Böszörményi
Subject Re: Strange Windows problem, lock_timeout test request
Date
Msg-id 510A85F2.7090806@cybertec.at
Whole thread Raw
In response to Re: Strange Windows problem, lock_timeout test request  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Strange Windows problem, lock_timeout test request
Re: Strange Windows problem, lock_timeout test request
List pgsql-hackers
2013-01-31 15:22 keltezéssel, Alvaro Herrera írta:
> 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 ...

It didn't occur to me to use "make installcheck" for this one.

What is strange though is why prepared_xacts_1.out exists
at all, since pg_regress.c / make check seems to set
max_prepared_transactions on Windows, too.

Is there a way to specify such settings in REGRESS_OPTS?

Best regards,
Zoltán Böszörményi

--
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: http://www.postgresql-support.de     http://www.postgresql.at/




pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Strange Windows problem, lock_timeout test request
Next
From: Andrew Dunstan
Date:
Subject: Re: Strange Windows problem, lock_timeout test request