Re: Strange Windows problem, lock_timeout test request

Поиск
Список
Период
Сортировка
От Zoltán Böszörményi
Тема Re: Strange Windows problem, lock_timeout test request
Дата
Msg-id 51093216.3030405@cybertec.at
обсуждение исходный текст
Ответ на Re: Strange Windows problem, lock_timeout test request  (Zoltán Böszörményi <zb@cybertec.at>)
Список pgsql-hackers
<div class="moz-cite-prefix">2013-01-30 15:29 keltezéssel, Zoltán Böszörményi írta:<br /></div><blockquote
cite="mid:51092E30.9040405@cybertec.at"type="cite">2013-01-28 15:20 keltezéssel, Hari Babu írta: <br /><blockquote
type="cite">OnSaturday, January 19, 2013 11:23 AM Amit kapila wrote: <br /><blockquote type="cite">On Saturday, January
19,2013 4:13 AM Boszormenyi Zoltan wrote: <br /><blockquote type="cite">Hi, <br /><br /> Unfortunately, I won't have
timeto do anything with my lock_timeout <br /></blockquote></blockquote> patch <br /><blockquote
type="cite"><blockquotetype="cite">for about 3 weeks. Does anyone have a little spare time to test it on <br
/></blockquote></blockquote>Windows? <br /><blockquote type="cite">I shall try to do it, probably next week. <br />
Othersare also welcome to test the patch. <br /></blockquote> I have carried out some windows testing of the lock
timeoutpatch. <br /></blockquote><br /> Thanks very much. It means it didn't crash for you and <br /> it waited the
expectedamount of time as well. <br /><br /><blockquote type="cite">The extra tests which are carried out on the patch
areattached in the mail. <br /></blockquote><br /> The patch itself contained regression tests to run by itself <br />
andcompete with statement_timeout as well, although <br /> it waits only 2 seconds instead of 60 as in your test. <br
/><br/><blockquote type="cite">Some observations on the patch: <br /><br /> 1. Patch needs a rebase as it causing some
rejections.<br /></blockquote><br /> On a fresh GIT pull, it only caused a reject for the documentation <br /> parts of
thepatch. No other rejects and no fuzz, only line shift <br /> warnings were indicated by the patch. Anyway, a
refreshedone <br /> is attached. <br /><br /><blockquote type="cite">2. regress check failed because the expected
".out"file is not updated <br /> properly. <br /></blockquote><br /> Which regress check failed? The .out file was
updatedin the patch <br /> for prepared_xacts.sql where the regression tests for lock_timeout <br /> were added. Or do
youmean the one for the sql file you sent? <br /></blockquote><br /> If the failed regression test is indeed the
prepared_xacts.sqlthat is<br /> in my patch, can you attach the regression.diff file after the failed<br /> "make
check"?Thanks.<br /><br /><blockquote cite="mid:51092E30.9040405@cybertec.at" type="cite"><br /> Thanks, <br /> Zoltán
Böszörményi<br /><br /><br /><br /><fieldset class="mimeAttachmentHeader"></fieldset><br /><pre wrap="">
 
</pre></blockquote><br /><br /><pre class="moz-signature" cols="72">-- 
----------------------------------
Zoltán Böszörményi
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt, Austria
Web: <a class="moz-txt-link-freetext" href="http://www.postgresql-support.de">http://www.postgresql-support.de</a>
<aclass="moz-txt-link-freetext" href="http://www.postgresql.at/">http://www.postgresql.at/</a>
 
</pre>

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Zoltán Böszörményi
Дата:
Сообщение: Re: Strange Windows problem, lock_timeout test request
Следующее
От: Andres Freund
Дата:
Сообщение: Re: autovacuum not prioritising for-wraparound tables