Hi, testing monetdb, I've come accross a query that takes several minutes on my dev machine (with only 2 GB of RAM). So it will swap for a while, and finally produce the result. I wanted to get the duration of the request, so I did 'set history=true;' The request takes a few minutes, and returns 464 tuples. But when I select from callHistory, here is the outcome : +---------+----------------------------+------------------+-------------+-------+------+--------+--------+---------+---------+ | id | ctime | arguments | xtime | rtime | foot | memory | tuples | inblock | oublock | +=========+============================+==================+============= +=======+======+========+========+=========+=========+ | 6776676 | 2009-07-21 13:25:27.000000 | user.s6_1(); | 22108050926 | 0 | 0 | 0 | 1 | 0 | 0 | +---------+----------------------------+------------------+-------------+-------+------+--------+--------+---------+---------+ Obviously, xtime is wrong (the query did not last for 6 hours). I guess rtime is also a bit quick :-) And the number of tuples is also wrong... Running the same query with \t in mclient gives: Timer 322316.803 msec 464 rows This seems more like truth. Well, I am conscious that with that information, it's hard to tell where the problem is.... So my question is rather: is the information in callHistory expected to be reliable, or more like an indication ? Franck