Kevin Grittner wrote: > > 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. > No problem at all to include my tests in the regression tests. I really like the fact that this project of mine can contribute to PostgreSQL.
-- View this message in context: http://postgresql.1045698.n5.nabble.com/BUG-6269-Anomaly-detection-tp4936233p4948383.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
