On 07/06/11 10:41, Adrian Reyer wrote:
> On Wed, Jul 06, 2011 at 10:09:56AM -0400, Phil Stracchino wrote:
>> should I use for my tables?" is MyISAM.[1] At this point, wherever
>> possible, EVERYONE should be using InnoDB.
>
> I will, if the current backup ever finishes. For a start on MySQL 5.1
> though (Debian squeeze). I am aware InnoDB has a more stable performance
> according to the posts I have found in various bacula-mysql related
> posts. Your post gives me some hope I can get away with converting the
> table format instead of migrating to postgres. Simple for the fact I
> have nicer backup scripts for mysql than for postgres.
Oh, sure. It's dead simple.
for table in $(mysql -N --batch -e 'select
concat(table_schema,'.',table_name) from information_schema.tables where
engine='MyISAM' and table_schema not in
('information_schema','mysql')'); do mysql -N --batch -e "alter table
$table engine=InnoDB" ; done
Keep in mind that on MySQL 5.1, you should preferably be using the
InnoDB plugin rather than the built-in InnoDB engine. The plugin InnoDB
engine is newer and performs better.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
[email protected] [email protected] [email protected]
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
