Hello! I'm running Oct2014-SP1 on a 64-bit Fedora 20 system and encountering another segmentation violation in mserver5. This time it happens quite often, making it nearly impossible to use the database. Before that started happening I also encountered these errors: GDK reported error. BATproject: does not match always when attempting a COPY INTO operation. One slightly suspicious factor is that the table being added to currently contains 3,995,238,028 records, just under the maximum for a 32-bit unsigned integer. Is there, in fact, a limit on how many records can be stored in a table? Or in any case, is there anything I can do about the errors? At this point any significant query on this table cause mserver5 to crash. The segmentation violation gets reported in the merovingian log, but all it says is database 'logs' (18717) was killed by signal SIGSEGV Before that there is nothing suspicious. Oh, one other strange thing is that, even when it is running, I can no longer query the status of the database with monetdb status The command generates an error: monetdb: cannot find a control socket, use -h and/or -p but this is a local database and the Unix domain sockets are there: /tmp/.s.monetdb.50000 /tmp/.s.merovingian.50000 /opt/farm/logs/.mapi.sock It seems like things have gone very wrong but I am not sure what to check. Thanks for any pointers you can give! Tim