I run a SQL statement about UPDATE covering multiple tables, i feel that it is
too slowly.
SQL statement:
update b_bb,tempdb set b_bb.zrk1=tempdb.num
where
b_bb.dwdm=concat(tempdb.shengbm,tempdb.shibm,tempdb.xianbm,tempdb.xiangbm,tempdb.cunbm);
I modify the JOIN syntax like this:
update b
I'm setting up mysql on linux for the first time (have been using OpenBSD and
NetBSD with UFS until now). The default file system is ext3fs, and I don't mind
that, but it seems really silly to use a journaled file system for the database
data - doubling my writes.
In particular, I have a coupl
Out of curiosity, how many queries/sec are you able to push from each
slave? If I may ask.. :)
Atle
On Mon, 5 Mar 2007, Ross Vandegrift wrote:
> On Fri, Mar 02, 2007 at 12:57:25AM -0800, Gary W. Smith wrote:
> > Pdns?
>
> Close! bind-dlz
>
> > Anyway, did you enable the slow query logging? Th
I'm trying to diagnose a server which is frequently racking up over
70% iowait when running a big PHP/MySQL app. I've increased mysql
memory allocations as far as I dare, but it's just not clear to me
where the problem is. My tables are all innodb, but the numbers in
'show innodb status' ar
Hi,
I suppose this is really I/O problem.
What says vmstat during backup?
I see many fsyncs, so you have probably innodb_flush_log_at_trx_commit=1
Try to set innodb_flush_log_at_trx_commit=2
If it solve your problem and you need innodb_flush_log_at_trx_commit=1,
install battery backed write
Hi Everyone,
I’m having a problem with a single repair query seemingly taking over the
whole server. I’ll try and explain….
Large table or 1.2m rows, running a repair on this causes the query queue to
grow and grow and finally max out.
The problem isn’t table locks because no-one else is
Jerad -
First of all, please reply all with a SHOW CREATE TABLE of the table
you're inserting the row into, so that we can identify the indexes
you've established for the table.
thanks,
--bemansell
On 3/7/07, jerad sloan <[EMAIL PROTECTED]> wrote:
when i try to insert the string "
http://vids.
Filip Krejci wrote:
> Hi,
>
> I suppose this is really I/O problem.
>
You're right, it looks like it was just an I/O problem - your suggestion
was spot on. I've now managed to dump my master data, and can get my
slave back online!
Thanks a lot for your suggestion,
--
Ian P. Christian ~ http://p
Filip Krejci wrote:
> Hi,
>
> you are right, option --single-transaction does not accquire any lock on
> your innodb tables. Backup is fully on-line due to mvcc.
>
> You should look for another reason of this behavior.
>
> 1/ What says 'show full processlist' when backup is running
> 2/ What says
In news:[EMAIL PROTECTED],
"Ian P. Christian" <[EMAIL PROTECTED]> wrote:
> This database I'm dumping has something like 17 million rows, all but
> 1 table (which uses FULLTEXT, and only has 3-4k rows) run innodb.
> There is only one table of any real size, and this table has all but
> about 100k o
10 matches
Mail list logo
