Hi Mathieu,
I found that innodb_buffer pool value isn't set..The whole innodb
settings are commented.
I found the below values from the my.cnf file:
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:auto
It is way past bed time so excuse me if I am way off...
What is the order of tables in the explain? What is shown as the select_type?
On 10/2/07, Eamon Daly <[EMAIL PROTECTED]> wrote:
> Hi, all. I couldn't find this mentioned in the docs or in
> the archives, so I'd figure I'd ask. I have a t
Thanks,
It helped me a lot. I wanted to know
1.. what are the various scenarios where my replication setup can fail?
(considering even issues like network failure and server reboot etc). What is
the normal procedure to correct the failure when something unpredicted happens?
2.. What are the
Hi, all. I couldn't find this mentioned in the docs or in
the archives, so I'd figure I'd ask. I have a table with a
multipart index on three columns. When querying the table
alone using IN operators on any of the three columns, all
parts of the index are used. However, if I do a JOIN with
another
--
Rob Wultsch
(480)223-2566
[EMAIL PROTECTED] (email/google im)
wultsch (aim)
[EMAIL PROTECTED] (msn)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Yes. Sorry, I wasn't verbose enough. I agree with you. And I also
agree that this part of the manual is kind of nonsensical. I have never
understood it fully. Part of what I was saying is "I wonder whether the
manual is wrong and you are getting a deadlock anyway."
William Newton wrote:
Thanks for the quick reply Barron, but doesn't SET AUTOCOMMIT = 0; disable
AUTOCOMMIT ?
from http://dev.mysql.com/doc/refman/5.0/en/lock-tables.html :
The correct way to use LOCK TABLES and
UNLOCK TABLES with transactional tables,
such as InnoDB tables, is t
Hi William,
William Newton wrote:
Hello List,
I discovered an unusual problem with the way Innodb handles the AUTO_INC lock
with a full table lock. I was wondering if this is a known issue, or I'm doing
something completely wrong. I'm working with MYSQL Server version:
5.0.42-debug-log on G
Hello List,
I discovered an unusual problem with the way Innodb handles the AUTO_INC lock
with a full table lock. I was wondering if this is a known issue, or I'm doing
something completely wrong. I'm working with MYSQL Server version:
5.0.42-debug-log on Gentoo Linux.
So lets say I have this
On Mon, 2007-10-01 at 12:56 -0700, Daevid Vincent wrote:
> This has been asked for many many times on this list, not sure why mySQL AB
> doesn't just release a command line tool like a 'mysql diff' and also a
> 'mysql lint'. The lint one should be totally trivial for them to do, as they
> already h
Ratheesh K J schrieb:
Hello all,
I issued a create table statement on the master for a table which was not
present on the master but present on the slave.
I did this purposely to see the error on slave.
I am a newbie to replication. Now when i see SLave status on the slave machine
it shows th
Hello all,
I issued a create table statement on the master for a table which was not
present on the master but present on the slave.
I did this purposely to see the error on slave.
I am a newbie to replication. Now when i see SLave status on the slave machine
it shows that the SQL Thread has st
12 matches
Mail list logo