Am 15.03.2012 17:31, schrieb Malka Cymbalista:
We are running MySQL version 5.0.45 on a Linux machine. Most of our tables
are MyIASM but we have recently installed drupal 7 and drupal 7 requires
INNODB tables. Every now and then when we restart MySQL using the commands
/etc/init.d/mysql
Hi,
Lets see If I can help.
Overly long queries (transactions
in general) are bad for performance as a lot of unpurged versions
accumulate.
In this sentence, I don't know the meaning about 'unpureged version
accumulate'
When rows are updated new versions are created. They are later
HI Peter:
Thanks for your answer. I have understand your answer. Thank you very
much.
――
Best regards
Timo Seven
blog: http://zauc.wordpress.com
#请翻墙浏览，或者指定hosts到74.200.243.252###
UNIX System Admin
2010/3/23 Peter Zaitsev p...@percona.com
Hi,
Lets see
Hi everyone:
I read the presentation about InnodDB performance optimization what
Heikki Tuuri written in april23 2007.
But now I have some sentences don't know how to understanding. Can you help
me?
Overly long queries (transactions
in general) are bad for performance as a lot of unpurged
On 9/7/06, Paul McCullagh [EMAIL PROTECTED] wrote:
It sounds like you program allows ad-hoc queries, so why don't you
just limit the number of rows returned by a select?
For example you could limit the number of rows to 1001. If the server
returns 1001, then display 1000 and tell the user
Hi Prasad
This question got me a bit interested as we're thinking of moving
some MyISAM tables to InnoDB and I haven't used it much.
I decided to test some of these ideas so I created an innodb table
and put some data into it and tried some selects:
(Running on MacBook Pro, 2.0ghz, 1gb
:[EMAIL PROTECTED]
Sent: Thursday, September 07, 2006 10:39 AM
To: Prasad Ramisetti (WT01 - Broadband Networks)
Cc: MySQL List
Subject: Re: problem with InnoDB
Hi Prasad
A primary key automatically creates an index and not-null and unique
constraints, too. So you don't need to explicitly create
:[EMAIL PROTECTED]
Sent: Thursday, September 07, 2006 10:39 AM
To: Prasad Ramisetti (WT01 - Broadband Networks)
Cc: MySQL List
Subject: Re: problem with InnoDB
Hi Prasad
A primary key automatically creates an index and not-null and unique
constraints, too. So you don't need to explicitly create
On 9/7/06, [EMAIL PROTECTED] wrote:
I need to know the number of rows that a query will return before
actually executing the query. So I am sending select count(*) before
sending select *. Actually I need to reject queries if the number of
records that it will return is huge, to avoid my server
On Sep 7, 2006, at 3:32 PM, [EMAIL PROTECTED] wrote:
I need to know the number of rows that a query will return before
actually executing the query. So I am sending select count(*) before
sending select *. Actually I need to reject queries if the number of
records that it will return is huge,
Networks)
Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: problem with InnoDB
In the last episode (Sep 04), [EMAIL PROTECTED] said:
Actually there is some requirement, where I need to know the number of
rows that I will get for my queries before actually executing the
query. Could you please
[EMAIL PROTECTED] wrote:
Hi Dan,
Thanks for yur response. Does it makes sense to create an index on a
primary key ..as that is my smallest field ?
A primary key already has an index.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
an index on a
primary key ..as that is my smallest field ?
Regards
Prasad
-Original Message-
From: Dan Nelson [mailto:[EMAIL PROTECTED]
Sent: Monday, September 04, 2006 9:53 AM
To: Prasad Ramisetti (WT01 - Broadband Networks)
Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: problem
In the last episode (Sep 07), [EMAIL PROTECTED] said:
Hi Dan,
Thanks for yur response. Does it makes sense to create an index on a
primary key ..as that is my smallest field ?
It might, because in an InnoDB table, your primary index also holds
your row data. So it's actually your largest
PROTECTED]
Sent: Wednesday, August 16, 2006 9:58 AM
To: Prasad Ramisetti (WT01 - Broadband Networks)
Cc: mysql@lists.mysql.com
Subject: Re: problem with InnoDB
[EMAIL PROTECTED] wrote:
Hi ,
select count(*) is painfully slow in case of innoDB when the number of
records are around 1 million. Ths
In the last episode (Sep 04), [EMAIL PROTECTED] said:
Actually there is some requirement, where I need to know the number
of rows that I will get for my queries before actually executing the
query. Could you please suggest some way for this.
Your best bet is to create an index on the smallest
Hi,
I am facing a strange problem with INNODB. My application communicates with
mysql server using JDBC. I am using mysql 5.1 version.
Even after issuing connection.commit() / connection.rollback() commands, still
on the sql side the transactions are not getting closed properly. In our
behavior).
R.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 23, 2006 9:31 AM
To: mysql@lists.mysql.com
Subject: Problem with INNODB transactions
Hi,
I am facing a strange problem with INNODB. My application communicates
with mysql server
Subject: RE: Problem with INNODB transactions
What connection pool code are you using? My guess is that the problem is
in your code somewhere. Either transactions are not being closed (i.e.
because of a connection pool flaw maybe?) or you have two threads trying
to update the same row at the same
Hi,
There is a problem with CPU utlization when using INNODB. The CPU
utilization goes to 100% in a dual processor solaris box. With the same
setup, myISAM uses only 60% of the CPU.
Could someone please let me know what could be the problem. There are
some other processes running on the same
Hi,
There is a problem with CPU utlization when using INNODB. The CPU
utilization goes to 100% in a dual processor solaris box. With the same
setup, myISAM uses only 60% of the CPU.
Could someone please let me know what could be the problem. There are
some other processes running on the same
[EMAIL PROTECTED] wrote:
Hi,
There is a problem with CPU utlization when using INNODB. The CPU
utilization goes to 100% in a dual processor solaris box. With the same
setup, myISAM uses only 60% of the CPU.
As I said before, stuff like 'count(*)' queries cannot use an index in
innodb - if
Hi ,
select count(*) is painfully slow in case of innoDB when the number of
records are around 1 million. Ths select count(*) query in myISAM takes
0.01 secs and the same query in InnoDB takes around 20.15 secs.
Can anybody suggest me how to speed up this query ?
Thanks
Prasad
The
[EMAIL PROTECTED] wrote:
Hi ,
select count(*) is painfully slow in case of innoDB when the number of
records are around 1 million. Ths select count(*) query in myISAM takes
0.01 secs and the same query in InnoDB takes around 20.15 secs.
Can anybody suggest me how to speed up this query ?
: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/mysql/en
Paul,
- Original Message -
From: Paul W [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Monday, October 25, 2004 11:33 AM
Subject: Cloned machine mysql startup problem with innodb
For backup purposes I have what amounts
to a complete clone of a live server.
During
For backup purposes I have what amounts
to a complete clone of a live server.
During the process of copying
everything, the MySQL data was copied
over in its entirety. My problem is that
the mysqld won't start now on this
second machine. I don't need the
databases to be preserved here
Heiki
Thx... it's work :D
Sorry, one liner
Heikki Tuuri [EMAIL PROTECTED] wrote:
Ady,
- Alkuperäinen viesti -
Lähettäjä: Ady Wicaksono
Vastaanottaja: Ady Wicaksono ; Heikki Tuuri
Kopio:
Lähetetty: Friday, September 03, 2004 10:41 AM
Aihe: Re: Problem on InnoDB - Tablespace enough
I try to detect using MC (Midnight Commander) and found that after
;/data4/ibdata25:1802M
it won't write anymore...
I remove these data file and add /ibdata1/ibdata10:1500M and /data1/ibdata11:1500M
I believe, All data below is empty but corrupt :(
data file defintion --
Ady,
- Alkuperäinen viesti -
Lähettäjä: Ady Wicaksono [EMAIL PROTECTED]
Vastaanottaja: Ady Wicaksono [EMAIL PROTECTED]; Heikki Tuuri
[EMAIL PROTECTED]
Kopio: [EMAIL PROTECTED]
Lähetetty: Friday, September 03, 2004 10:41 AM
Aihe: Re: Problem on InnoDB - Tablespace enough but engine said
Ady,
InnoDB thinks that the tablespace size is 10 706 MB.
You have specified 36 782 MB of data files in the my.cnf line :(.
Now you should figure out what are the data files that InnoDB is using, and
remove the end of the innodb_data_file_path line, as well as the unused
ibdata files. Remember
May i know, how could i know which of the data files that InnoDB MySQL engine is not
used ?
Did i i made a mistake when adding table space ?
Heikki Tuuri [EMAIL PROTECTED] wrote:
Ady,
InnoDB thinks that the tablespace size is 10 706 MB.
You have specified 36 782 MB of data files in the
I have MySQL for heavy duty job .
here is my InnoDB table space definition
innodb_data_file_path =
/data0/ibdata1:10M;/data0/ibdata2:10M;/data0/ibdata3:1082M;/data0/ibdata4:1500M;/data0/ibdata5:1500M;/
syntax from your my.cnf file?
-Original Message-
From: Hugh Taylor
To: [EMAIL PROTECTED]
Sent: 7/12/04 3:17 PM
Subject: Problem getting innodb enabled ...
Running MySQL 4.0.15 on SuSE 9 Professional. MySQL works fine until I
try to allow innodb by uncommenting the lines in the my.cnf file
After much searching (and trying to read non-English posts), I've
stumbled across the solution. I installed the mysql-MAX rpm, changed the
my.cnf file and Viola! it works!
--
Hugh
mailto: [EMAIL PROTECTED]
Hugh Taylor wrote:
Running MySQL 4.0.15 on SuSE 9 Professional. MySQL works fine until I
Running MySQL 4.0.15 on SuSE 9 Professional. MySQL works fine until I
try to allow innodb by uncommenting the lines in the my.cnf file. Once I
do this MySQLwill not start, the error message in the log is:
040712 15:25:39 mysqld started
/usr/sbin/mysqld: ERROR: unknown variable
Can you post the exact syntax from your my.cnf file?
-Original Message-
From: Hugh Taylor
To: [EMAIL PROTECTED]
Sent: 7/12/04 3:17 PM
Subject: Problem getting innodb enabled ...
Running MySQL 4.0.15 on SuSE 9 Professional. MySQL works fine until I
try to allow innodb by uncommenting
i am new to mysql,
my problem is that i cannot create tables with type innodb
i have made the entry innodb_data_file_path in my.cnf
i am using mysql 4.0.2 alpha on red hat 7.1
could anybody plese help me?
thanks
anirudh
-
a table scan.
Regards,
Heikki
Innobase Oy
sql query
- Original Message -
From: Natale Babbo [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, January 14, 2003 5:52 PM
Subject: please help me - problem with innodb foreign keys
# - PLEASE HELP -- #
hi,
i've a problem
David,
Wednesday, November 06, 2002, 10:00:45 PM, you wrote:
DAF - Original Message -
DAF From: Victoria Reznichenko [EMAIL PROTECTED]
DAF To: [EMAIL PROTECTED]
DAF Sent: Wednesday, November 06, 2002 11:47 AM
DAF Subject: re: Problem creating InnoDB tables.
David,
Tuesday, November 05
David,
Tuesday, November 05, 2002, 4:05:57 PM, you wrote:
DAF I'm have trouble creating InnoDB tables. I'm using MySQL version
DAF 3.32.51-max. I have innodb_data_file_path = ibdata1:30M:autoextend in my
DAF my.ini file. According to the manual, I should be able to use and create
DAF InnoDB
- Original Message -
From: Victoria Reznichenko [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 06, 2002 11:47 AM
Subject: re: Problem creating InnoDB tables.
David,
Tuesday, November 05, 2002, 4:05:57 PM, you wrote:
DAF I'm have trouble creating InnoDB tables. I'm
Hello,
I'm have trouble creating InnoDB tables. I'm using MySQL version
3.32.51-max. I have innodb_data_file_path = ibdata1:30M:autoextend in my
my.ini file. According to the manual, I should be able to use and create
InnoDB tables. When I specify type = InnoDB in my table creation
statement,
Hello,
I've just switched to InnoDB table from myISAM and it's been running pretty smoothly
except on this SQL statement it doesn't use any indexes when there are, and therefore
is very slow.
mysql explain select
pn.timestamp,ne.viewpoint,pn.id,pn.type,ne.type,ne.newsid,ne.hidestamp from
Sounds good. Thanks for the info, Heikki.
--Walt
-Original Message-
From: Heikki Tuuri [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 23, 2002 11:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Benchmarking MyISAM, InnoDB, and Oracle: a problem with
InnoDB
Walt,
this is probably
Hey,
I dunno whether it's a bug or just I don't know how to use transactions
properly. I've got 3.23.36 on FreeBSD 4.2-STABLE, and when I do this:
CREATE TABLE test TYPE=Innobase SELECT * otherdb.sometable;
MySQL hangs. If I limit the SELECT query to 10-100 rows, it executes quite
fast (same
46 matches
Mail list logo
