[rt-users] sessions table is lost after a system crash

Ruslan Zakirov ruslan.zakirov at gmail.com
Fri Apr 24 07:06:16 EDT 2009

On Fri, Apr 24, 2009 at 1:23 AM, Tim Cutts <tjrc at sanger.ac.uk> wrote:
> On 23 Apr 2009, at 6:54 pm, Tom Lahti wrote:
>> Kenneth Marshall wrote:
>>> Tim,
>>> I am curious. Are you using InnoDB tables or MyISAM tables?
>>> I thought that RT needed InnoDB. Does it have a problem with
>>> system crashes and recovery with InnoDB?
>>> Just wondering.
>>> Ken
>> I was just about to say the same thing when this came in.  I think
>> you want
>> InnoDB tables, not MyISAM.  In particular, large tables like the
>> attachment
>> table will have problems, and frequently updated tables like the
>> session
>> table will have crash recovery issues.  The crash recovery in the
>> InnoDB
>> backend is more robust, as is the indexing methodology.
> Preaching to the choir.  In a default RT installation on MySQL, all
> the tables are InnoDB *except* for the sessions table.  I don't know
> why that particular table is MyISAM, and I don't know whether there
> would be any consequences of converting it.

No consequences, it's just legacy.

> Tim
> --
>  The Wellcome Trust Sanger Institute is operated by Genome Research
>  Limited, a charity registered in England with number 1021457 and a
>  company registered in England with number 2742969, whose registered
>  office is 215 Euston Road, London, NW1 2BE.
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com

Best regards, Ruslan.

More information about the rt-users mailing list