OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Jason Stajich (jasonchg.mc.duke.edu)
Date: Mon Apr 02 2001 - 13:13:24 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    I just saw the post on the web, have not had a chance to subscribe to the
    list, apologies if you have already had this answered...

    I had a similar scenario on an openbsd x86 box where I was loading data
    with mysqlimport. I was able to solve the problem you describe upgrading
    to mysql 3.23.36. I saw some information documenting the bug, but can't
    seem find that now -- maybe in cvs log msg? Anwyays, upgrading my ports
    package and installing the newer version makes it all work for me.

    While I'm writing, I do run into my own problems when I try and load a
    table that is about 6 GB. I can load up to about 4.2GB and then it chokes
    -- table is full message. Mysql doc says the --big-tables flag is not
    necessary as srv adjusts automatically, but even including that flag I
    cannot make data load more than 4.3GB (by that I mean what the table size
    is in data/dbname/table.MYD). This is from a mysqldump from mysqldb
    running on an alpha. I can load this data into a mysql db running on
    solaris, but not openbsd 2.8 x86. I can't seem to find documentation on
    filesize limitations on openbsd. But I know that mysql can handle files
    this large on other OSes.

    Jason Stajich
    jasonchg.mc.duke.edu
    Center for Human Genetics
    Duke University Medical Center
    http://www.chg.duke.edu/