Thanks Hannes,
Do you mean you don't get a SIGSEGV but a failure like in my first example (aggr_group), or do you get a correct result?
I am using Jul2015 updated to yesterday, 30 Sept 2015
Below the SIGSEGV.
This conversation should probably be in a bug report, I first posted it here because the 200000 looked too strange to be a coincidence, I thought it could have been due to some hard-coded debug limitation.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f5d31e00700 (LWP 29057)]
0x00007f5d3499cf10 in RAPIeval (cntxt=0x7f5d35a12328, mb=0x7f5d2431cbe0, stk=0x7f5d24270ec0, pci=0x7f5d24270230, grouped=1 '\001') at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/monetdb5/extras/rapi/rapi.c:518
518 BAT_TO_REALSXP(b, lng, varvalue);
(gdb) bt
#0 0x00007f5d3499cf10 in RAPIeval (cntxt=0x7f5d35a12328, mb=0x7f5d2431cbe0, stk=0x7f5d24270ec0, pci=0x7f5d24270230, grouped=1 '\001') at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/monetdb5/extras/rapi/rapi.c:518
#1 0x00007f5d3499b276 in RAPIevalAggr (cntxt=0x7f5d35a12328, mb=0x7f5d2431cbe0, stk=0x7f5d24270ec0, pci=0x7f5d24270230) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/monetdb5/extras/rapi/rapi.c:387
#2 0x00007f5d3d21766e in runMALsequence (cntxt=0x7f5d35a12328, mb=0x7f5d2431cbe0, startpc=39, stoppc=40, stk=0x7f5d24270ec0, env=0x0, pcicaller=0x0) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/monetdb5/mal/mal_interpreter.c:631
#3 0x00007f5d3d21c9be in DFLOWworker (T=0x7f5d3d696900 <workers+128>) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/monetdb5/mal/mal_dataflow.c:376
#4 0x000000394d007555 in start_thread () from /lib64/libpthread.so.0
#5 0x000000394cd02b9d in clone () from /lib64/libc.so.6