;
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 9:59 PM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
John,
please zip ibdata1, which is 'only' 100 MB, and upload it when you
have shut
down mysqld.
I have been s
ww.innodb.com/order.php
Order MySQL technical support from https://order.mysql.com/
- Original Message -
From: ""Heikki Tuuri"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 9:59 PM
Subject: Re: InnoDB data files keep grow
<[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 8:17 PM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki,
Heikki Tuuri wrote:
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routi
Sasha,
- Original Message -
From: "Sasha Pachev" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 8:05 PM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki Tuuri wrote:
Ivan,
hmm... could it be that s
Heikki,
Heikki Tuuri wrote:
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routine first prints inode pages
that are completely used, and after that other inode pages. Since the
tablespace validation said the tablespace is ok, I guess
Heikki Tuuri wrote:
Ivan,
hmm... could it be that segments 0 1, 0 2, 0 3, etc. were printed close
to the end of the output? The print routine first prints inode pages
that are completely used, and after that other inode pages. Since the
tablespace validation said the tablespace is ok, I guess th
Heikki,
Heikki Tuuri wrote:
InnoDB is clearly leaking 'segments' in the system tablespace. They are
probably undo logs. For some reason, a trx commit or purge fails to free
them.
SEGMENT id 0 75994 space 0; page 82136; res 2720 used 2680; full ext 41
fragm pages 32; free extents 0; not full exte
ling.database.myodbc
Sent: Thursday, November 11, 2004 10:16 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Ivan,
- Original Message -
From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
S
1, 2004 10:16 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Ivan,
- Original Message -
From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 4:55 AM
Subject: Re: InnoDB data files
Ivan,
- Original Message -
From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 4:55 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki,
the output shows that there ar
Heikki,
I can think of another explanation. Are you sure that all your tables
really are in .ibd files? Maybe some older tables are actually in the
ibdata files?
Yes I'm sure they're all in .ibd files (and I've just checked just in case
- they are indeed).
Please use the innodb_tablespace_monito
Heikki,
the output shows that there are no dangling transactions, and purge is
not lagging behind.
Yes, that's what I thought... weird, huh :/
If you update a secondary index column, that requires purge to clean up
the index.
The tables have structure similar to the following:
create table table1
uot;Heikki Tuuri"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Thursday, November 11, 2004 1:55 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
John,
the output shows that there are no dangling transactions, and purge is not
lagging behind.
Message -
From: ""John B. Ivski"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Wednesday, November 10, 2004 4:25 AM
Subject: Re: InnoDB data files keep growing with innodb_file_per_table
Heikki,
Heikki Tuuri wrote:
> John,
>
> please pos
Heikki,
Heikki Tuuri wrote:
> John,
>
> please post what SHOW INNODB STATUS says. The probable reason is that
> there are long transactions, or that purge is falling behind.
>
> Best regards,
>
> Heikki Tuuri
Actually, I have no idea why purge was falling behind, since no row has ever been deleted
John,
please post what SHOW INNODB STATUS says. The probable reason is that there
are long transactions, or that purge is falling behind.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also
16 matches
Mail list logo