When working with RELEASE version of MonetDB5 every once in a while I would enter in a bad query into mclient and it would crash the entire server hard - it would not even reboot. I did notice, however, that in the nightly stable release this same issue is handled better, in that it no longer crashes the server (very good news!). However it does result in mclient terminating the connection and closing. Here is how you can reproduce this: 1) run merovingian 2) mclient -lsql --time --database=demo 3) enter this query: sql>select avg(1); and you will get this: MAPI = monetdb@localhost:50000 ACTION= read_line QUERY = select avg(1); ERROR = Connection terminated Timer 3.049 msec <mclient exits> [bash ~] # Am I correct to assume this is not expected behavior? Thanks.