On 30-01-2009 21:59:15 -0600, Ross Bates wrote:
The original email was about how to stop an export process. Here's another related example, if you open things up to users and someone kicks off a query with a cartesian join there is no way to connect to the mserver5 process and kill that individual query without interrupting other queries. Another thing Dariusz inquired about in an earlier email was mserver5 logging. These are all traditional DBA items which are not available in MonetDB. It's really more a perception issue, if you call something a database people are going to have a natural tendency to compare to the other databases they've worked with.
I think you address two interesting points here. The first being to be able to shoot a client, e.g. think of MySQL's 'KILL <tid>;' syntax (by the way, that most of the time doesn't work when you really need it, for instance when something's locked, but that aside), and the second being a request for logging information. As creator of Merovingian, I had the latter one in mind when I wrote it. Merovingian's log hence shows some information about what it is doing, as well as what mserver5 processes write out, which usually only are errors and warnings. What kind of logging information are you looking for? Please note that Merovingian is not available on the Windows platform. As to the possibility to kill a client, perhaps we can just create a hook at the MAL level. It is worth to open up a feature request for this, I think.