Well ok was wondering about the out of memory thing but it all happens to fast as RAM does take a little time to fill the termination happens in a few seconds.

I will perform the step by step trace and the monitor metrics.
On Jan 28, 2013 6:49 PM, "Niels Nes" <Niels.Nes@cwi.nl> wrote:
>
> On Mon, Jan 28, 2013 at 06:44:20PM +0000, Brian Hood wrote:
> > Hi Martin,
> >
> > I don't believe my database is corrupt is there anyway in MonetDB to
> > check the integrity of data ?
> >
> > http://pastebin.com/3u4vX4TN - GDB Session
> Brian
>
> Did you by any change run out of memory?
> The trace you show indicates that Monet crashes in the Hash join
> operator, which is a used quite offten (doesn't help us much in pointing
> out why /where in the plan it crashes).
>
> (could you possibly run your query prefixed by 'debug')
> And the single step through your 'mal' plan.
>
> Niels
> >
> > http://pastebin.com/0cUVQwjU - Terminal Session for the SQL i was
> > running.
> >
> > Hope this helps.
> >
> > Brian Hood
> >
> > On Sun, Jan 27, 2013 at 7:42 PM, Martin Kersten <Martin.Kersten@cwi.nl>
> > wrote:
> >
> >     Assuming your database was not corrupted in the first place and the
> >     error is reproducable, it would help to  see the stack trace.
> >
> >     TO get it on a Linux box, use 'ps' to get the process id of the
> >     database server, call 'gdb mserver <processid>' and let it continue
> >     to run. Then re-issue the query, which should lead to gdb to report
> >     on the error.
> >
> >     The command 'thr apply all where' would show what all threads are
> >     doing during the crash.
> >
> >     thanks, Martin
> >
> >
> >     On 1/27/13 8:37 PM, Brian Hood wrote:
> >
> >         Yes i'm always joining on the guid field which is the primary
> >         key on all
> >         3 tables.
> >
> >         Ok thankyou initial findings are as follows tablec is by no
> >         means
> >         correct which i'll have to investigate however it still
> >         shouldn't of
> >         crashed the database but maybe of causing some serious main
> >         memory
> >         allocation trying to join it.
> >
> >         however tableb also isn't quite correct either about 300 or so
> >         rows out.
> >
> >     _______________________________________________
> >     users-list mailing list
> >     users-list@monetdb.org
> >     http://mail.monetdb.org/mailman/listinfo/users-list
> >
> >
>
> > _______________________________________________
> > users-list mailing list
> > users-list@monetdb.org
> > http://mail.monetdb.org/mailman/listinfo/users-list
>
>
> --
> Niels Nes, Centrum Wiskunde & Informatica (CWI)
> Science Park 123, 1098 XG Amsterdam, The Netherlands
> room L3.14,  phone ++31 20 592-4098     sip:4098@sip.cwi.nl
> url: http://www.cwi.nl/~niels   e-mail: Niels.Nes@cwi.nl
>
> _______________________________________________
> users-list mailing list
> users-list@monetdb.org
> http://mail.monetdb.org/mailman/listinfo/users-list
>