Fabien COELHO <coe...@cri.ensmp.fr> writes:
>> I have a serious, serious dislike for tests that seem to work until
>> they're run on a heavily loaded machine.
> I'm not that sure the error message was because of that.
No, this particular failure (probably) wasn't. But now that I've realized
that this test case is timing-sensitive, I'm worried about what will
happen when it's run on a sufficiently slow or loaded machine.
>> I would not necessarily object to doing something in the code that
>> would guarantee that, though.
> Hmmm. Interesting point.
It could be as simple as putting the check-for-done at the bottom of the
loop not the top, perhaps.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
