Memory tests were run and no problems were reported. With MonetDB+bad memory I would expect to lose some data and no data was lost here.
73, Matthew W. Jones (KI4ZIB) http://matburt.net
On Tue, Nov 24, 2009 at 8:59 AM, Sam Mason sam@samason.me.uk wrote:
On Mon, Nov 23, 2009 at 08:35:49PM +0100, Niels Nes wrote:
On Mon, Nov 23, 2009 at 02:30:14PM -0500, Matthew Jones wrote:
That actually worked... I recreated that file with the contents that I mentioned below and everything came back up. Very interesting that that file was empty after the crash.
Great, now I just have to find out why the file was empty.
This couldn't be a case of bad memory could it? I'm more of a user of Postgres and it happens surprisingly often there---i.e. PG misbehaves, user goes away and runs a RAM tester and it reports some bad memory.
Symptoms are about right; code running for a reasonable amount of time with what (in my experience, but not sure if this applies here) is normally a regular workload and spontaneously something breaks.
-- Sam http://samason.me.uk/
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users