Yes that makes sense, thanks Heikki.
I monitored the ib_logfiles some more and see
the cycling between pairs logfile0+logfile1 and
logfile0+logfile2.
Heikki Tuuri wrote:
John,
- Original Message -
From: "John Thorpe" <[EMAIL PROTECTED]>
I am running 4.0.4 using innodb tables on a linux bo
John Thorpe wrote:
524288000 Mar 11 11:19 ib_logfile0
524288000 Mar 3 08:59 ib_logfile1
524288000 Mar 11 11:19 ib_logfile2
I would venture a random guess that ib_logfile1 was in use until Mar 3,
then ib_logfile2 began and that around Mar 11 it switched back up to
ib_logfile0 where it st
John,
- Original Message -
From: "John Thorpe" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, March 11, 2004 7:34 PM
Subject: Innodb logfiles timestamp question
> Hi,
>
> I am running 4.0.4 using innodb tables on a linux box
Hi,
I am running 4.0.4 using innodb tables on a linux box.
My innodb config is
innodb_data_file_path = ibdata1:1800M;ibdata2:1800M;...ibdata10:1800M
set-variable = innodb_mirrored_log_groups=1
set-variable = innodb_log_files_in_group=3
set-variable = innodb_log_file_size=500M
set-variable = innod
ED]>
Sent: Wednesday, May 09, 2001 7:16
Subject: timestamp question
> I'm getting an error when creating a new database table with a timestamp
> column with
> NOW()...i.e. >> .., meetingtime timestamp(12) NOW(),
>
> I can't find an example in the mysql manual of
I'm getting an error when creating a new database table with a timestamp
column with
NOW()...i.e. >> .., meetingtime timestamp(12) NOW(),
I can't find an example in the mysql manual of how this is actually done. Can
anyone point me in the right direction.
Thanks,
Mark
--