goudvis <paul.staper...@gmail.com> wrote: > Robert Haas wrote: >> >> I would be curious to see (updated, corrected) results on older >> versions. > > If I am correct, Kevin Grittner is writing a review of the code > and the testing methods. I think it would be wise to wait for the > outcome of this. Afterwards, I could post the code and the > execution instructions for anyone who wants to test his or her > system. Another approach is to do the testing myself, but I don't > know when I have the time. Actually, since we (mostly you) found explanations for all the disallowed phenomena, with no PostgreSQL anomalies showing when using the corrected test code, I was going to call it done. Well, except that I think some of your tests are interesting enough to ask whether it was OK to try to integrate some of the related SQL into C-based tests in the optional PostgreSQL regression tests. (They probably run too long to include in the main "make check" set.) If I could get them running in that environment, I think they could stress a different-enough set of code paths to be worth including. Regarding the Java code used in your tests, the only issues I found which I didn't mention to you off list were stylistic or performance-related. Since the performance issues would apply to both MySQL and PostgreSQL, I'm not too worried about them in terms of comparative numbers. I anyone wanted to consider the absolute numbers as significant, I could pass along a few tips. -Kevin
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
