you had,
it should be 'undo1' not just '1'
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_tablespaces
So, that simple '1' file also seems unusual to me.
--
Shawn Green
MySQL Principal Technical Support Engineer
Oracle USA, Inc. - Hardw
;1.ibd'. That would be expected. But
> that seems unlikely based on your other details.
>
> Did you also enable a separate undo log, perhaps? Although if you had, it
> should be 'undo1' not just '1'
> http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.h
n your other details.
Did you also enable a separate undo log, perhaps? Although if you had, it
should be 'undo1' not just '1'
http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_undo_tablespaces
So, that simple '1' file also seems unusual to me.
We recently changed from in memory files to InnoDB files. Today we
noticed that in every server's data dir there is file called '1' that
seems to get updated every time the iddata1 file gets updated. On some
servers it's comparable in size to the iddata1 file, on other servers
it's 10-15x larger, a
On Wed, Jul 3, 2013 at 11:34 AM, Peterson, Timothy R
wrote:
>
>
>> -Original Message-
>> From: Larry Martell [mailto:larry.mart...@gmail.com]
>> Sent: Wednesday, July 03, 2013 11:29 AM
>> To: shawn green
>> Cc: mysql@lists.mysql.com
>> Subject: Re
> -Original Message-
> From: Larry Martell [mailto:larry.mart...@gmail.com]
> Sent: Wednesday, July 03, 2013 11:29 AM
> To: shawn green
> Cc: mysql@lists.mysql.com
> Subject: Re: 1 file
>
> On Wed, Jul 3, 2013 at 9:51 AM, shawn green
> wrote:
> > Hello
Cc: mysql@lists.mysql.com
> Subject: Re: 1 file
>
> On Wed, Jul 3, 2013 at 9:51 AM, shawn green
> wrote:
> > Hello Larry,
> >
> >
> > On 7/3/2013 11:27 AM, Larry Martell wrote:
> >>
> >> We recently changed from in memory files to InnoDB f
ssage-
>> From: Larry Martell [mailto:larry.mart...@gmail.com]
>> Sent: Wednesday, July 03, 2013 9:29 AM
>> To: shawn green
>> Cc: mysql@lists.mysql.com
>> Subject: Re: 1 file
>>
>> On Wed, Jul 3, 2013 at 9:51 AM, shawn green
>> wrote:
>>
to InnoDB. We can't
> do that however on another server, which we turned debugging on
> instead. It appears to be an assertion failure, the error message from
> the MySQL debugging code is:
>
> Assertion failed: fixed == 1, file item.h, line 1601
>
>
> Any help is greatly
eries per second. We've fixed the
issue on one of the servers by changing its tables to InnoDB. We can't
do that however on another server, which we turned debugging on
instead. It appears to be an assertion failure, the error message from
the MySQL debugging code is:
Assertion failed: f
e
issue on one of the servers by changing its tables to InnoDB. We can't
do that however on another server, which we turned debugging on
instead. It appears to be an assertion failure, the error message from
the MySQL debugging code is:
Assertion failed: fixed == 1, file item.h, line 1601
Any
> >
> > which would essentially make each table a file on it's own rather than
> > have it all in 1 file.
> > My belief is that it would be slightly more advantageous compared to 1
> > BIG file.
> >
> > eg: 1 10GB file would perform poorer than 10 1GB fil
On Mon, 2006-10-09 at 15:42 -0600, James Eaton wrote:
> - Original Message -
> From: "Bruce Dembecki" <[EMAIL PROTECTED]>
> To:
> Cc: "Ow Mun Heng" <[EMAIL PROTECTED]>
> How do you go about converting InnoDB databases from the single tablespace
> to those using the table-per-file file o
- Original Message -
From: "Bruce Dembecki" <[EMAIL PROTECTED]>
To:
Cc: "Ow Mun Heng" <[EMAIL PROTECTED]>
Sent: Monday, October 09, 2006 3:13 PM
Subject: Re: InnoDB, 1 file per table or 1 BIG table?
There are some minor performance benefits here whe
On Oct 9, 2006, at 7:15 AM, Ow Mun Heng wrote:
Hi All,
Just wanted to know if it would be faster/better to implement this
option into my.cnf
innodb_file_per_table = 1
which would essentially make each table a file on it's own rather than
have it all in 1 file.
My belief is that it wou
In the last episode (Oct 09), James Eaton said:
> From: "Dan Nelson" <[EMAIL PROTECTED]>
> >I don't think that the number of files has any impact on query
> >speed. The advantage file-per-table gives you is the ability to
> >recover unused space easily by running OPTIMIZE TABLE. With a
> >single t
- Original Message -
From: "Dan Nelson" <[EMAIL PROTECTED]>
To: "Ow Mun Heng" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, October 09, 2006 9:12 AM
Subject: Re: InnoDB, 1 file per table or 1 BIG table?
In the last episode (Oct 09), Ow Mun Heng said:
Ju
In the last episode (Oct 09), Ow Mun Heng said:
> Just wanted to know if it would be faster/better to implement this
> option into my.cnf
>
> innodb_file_per_table = 1
>
> which would essentially make each table a file on it's own rather
> than have it all in 1 file.
Hi All,
Just wanted to know if it would be faster/better to implement this
option into my.cnf
innodb_file_per_table = 1
which would essentially make each table a file on it's own rather than
have it all in 1 file.
My belief is that it would be slightly more advantageous compared to 1
BIG
Hello.
If you have such a big database, may be you should think about
--tab option of mysqldump:
http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html
Tom Brown wrote:
> is it possible to do a mysql dump to more than 1 file? We will shortly
> be needing to dump a db tha
The output of mysqldump is standard output, not a file. You can pipe
it into another program, or redirect the output to a file, but
mysqldump does not make a file. Therefore, there is no option in
mysqldump to make more than 1 file.
How is your database stored on disk? The documentation
The output of mysqldump is standard output, not a file. You can pipe
it into another program, or redirect the output to a file, but
mysqldump does not make a file. Therefore, there is no option in
mysqldump to make more than 1 file.
How is your database stored on disk? The documentation
At 3:56 PM + 11/21/05, Tom Brown wrote:
is it possible to do a mysql dump to more than 1 file? We will
shortly be needing to dump a db that will be in excess of 50gb so
will encounter file size issues
This is on 4.1.x and rhel 4
Probably the best approach - knowing nothing about your
The output of mysqldump is standard output, not a file. You can pipe
it into another program, or redirect the output to a file, but
mysqldump does not make a file. Therefore, there is no option in
mysqldump to make more than 1 file.
How is your database stored on disk? The documentation Edwin
en/mysqldump.html
Regards!!
Edwin Cruz
-Mensaje original-
De: Tom Brown [mailto:[EMAIL PROTECTED]
Enviado el: Lunes, 21 de Noviembre de 2005 09:57 a.m.
Para: mysql@lists.mysql.com
Asunto: dump to more than 1 file
is it possible to do a mysql dump to more than 1 file? We will shortly
be needin
is it possible to do a mysql dump to more than 1 file? We will shortly
be needing to dump a db that will be in excess of 50gb so will encounter
file size issues
This is on 4.1.x and rhel 4
thanks
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe
Ang,
Thursday, April 04, 2002, 4:21:10 PM, you wrote:
AHK> Is MySQL capable of storing files (*.doc *.zip etc)? If YES,
AHK> - is there a limit to the size?
AHK> - what is the data type to use? BLOB?
Yes, you should use BLOB types (TINYBLOB, BLOB, MEDIUMBLOB, LONGBLOB).
You can read about
Stelian Anton writes:
> Hello All,
>
> When I check to running the mysql_install_db I have the error:
>
> root@gem:/usr/local/mysql>scripts/mysql_install_db
>
> ld.so.1: ./bin/my_print_defaults: fatal: libcrypt_i.so.1: open failed: No such file
>or directory
>
> Environment:
>
> Sys
Hello All,
When I check to running the mysql_install_db I have the error:
root@gem:/usr/local/mysql>scripts/mysql_install_db
ld.so.1: ./bin/my_print_defaults: fatal: libcrypt_i.so.1: open failed: No such file or
directory
Environment:
System: SunOS gem 5.6 Generic_105181-23 sun4u sp
29 matches
Mail list logo
