[Monetdb-developers] stable xq testweb
P.Boncz at cwi.nl
Sun Feb 8 12:05:17 CET 2009
(the below analyis of the Stable XQ testweb is not an implicit request for
anybody to do something, I just share it here so you will not do double
Recently I checked in some fixes.
- Because I have the suspicion that certain scripts at NFI may still use
hard commits, I redefined the commit() in module pathfinder to giving an
- I also added pflock_trycommit(), as part of the change (hack?) to ensure
that checkpoint flushes occur only on an idle system.
This led me to expect the Stable testweb in detail today.
My new commit() error policy causes the following tests to display different
I think what we could do is to substitute the commit() by a pf_logflush(0LL)
, although simply omitting the "commit();"should also work.
The pflock_trycommit() new command obviously alsoshows up in some tests.
However, I also saw time-, standoff- and pf-tjah related output that
probably can be approved:
No to the oher differences (ignoring xrpc and W3c/qn/ns which AFAIK has
The below use recursive functions for which we maybe could add 'declare
option pf:recursion-depth "<number>";??
which leaves us with 6 the following suspect regressions:
More information about the developers-list