Hi Martin, Thanks for the help. On Jun 2, 2011, at 7:52 AM, Martin Kersten wrote:
If this happens during the COPY into statement, then most likely it is related to enforcing integrity constraints e.g. foreign keys.
Good to know. Unlikely to be the problem in my case though, as I actually decided *not* to define any constraint on this table at all, not even a primary key. Is there any performance benefit in MonetDB in defining primary keys or foreign keys?
Alternatively, a previous system failure (e.g. kill by the OS left it in an inconsistent state. If you can simply start the server and perform a simple query 'select 1;' then you at least know that the database itself is not corrupted.
This one will go in my fresh collection of MonetDB troubleshooting tips ;-) Definitely useful. I can not even start start the database at all (SIGSEGV) though. Stefan helped me generate a more meaningful stack trace in case you are interested: http://sourceforge.net/mailarchive/message.php?msg_id=27593226 Thanks again, - Philippe