hi,
Thank you for your reply :-)
What does replication have to do with it?
I wonder whether mysql will copy its binlog from memory( if it exists
) then send to slave. I haven't refer to the source codes yet...
Slave's binlog? The slave's binlog is not tied to the master's
binlog. I am not
Use o código de desconto NOSSOSITE e receba 10% de desconto em todas as suas
compras
Temos os melhores preços do Mercado. Se você encontrar um preço menor não
faremos o mesmo preço.
Você esta recebendo este por causa da sua relação com Gemas Brasil . Por favor
confirme o seu interesse em
Hi Rolando,
I am going to give it a try, but the thing is that the creation of index
with MyISAM table causes
a re-copy of the table (using temporary table) and so it is the same thing,
and seens to take a lot of time.
I stopped it after 10 hours or so.
I think is the way mysql manages the
Yes I killed several times the query but now way, the server was continuing
to hog disk space and not even shutdown worked!
Thanks!
Claudio
2009/2/27 Brent Baisley brentt...@gmail.com
MySQL can handle large tables no problem, it's large queries that it
has issues with. You couldn't just kill
Hi,
On Fri, Feb 27, 2009 at 2:51 PM, dbrb2002-...@yahoo.com wrote:
Thanks for the quick followup Baron..
vmstat
procs ---memory-- ---swap-- -io --system--
-cpu--
r b swpd free buff cache si so bi bo in cs us sy id
wa st
3 0 100
At 07:38 PM 2/25/2009, you wrote:
not sure, though, feel free to report test results
Results not good so far. I created a big load file
Then I did a LOAD DATA CONCURRENT INFILE 'my_big_file'...
While that was running, I ran a SELECT COUNT(*) query in another session.
The latter was blocked
Hi PJ,
Having been a C programmer for a while this makes perfect sense to me.
You call mysql_(real)_query to execute the query and get the results
from the server. Because the MySQL library doesn't know when you've
finished with the result-set, you have to tell it to write the results
to
hi,
It seems that mysql will call write interfaces(eg. bulk_update_row
ha_update_row ...) of HANDLER before writing a binlog.
Does this mean the time when binlog is written actually vary from
engine to engine?
Thank you.
--
MySQL General Mailing List
For list archives: