I've already opened a support ticket with MySQL on this issue, but
thought someone here might know the answer, too:
Hi there,
I'm trying to make sure I'm not doing something stupid. I'm trying to
migrate from 4.0 to 4.1, but I'm hitting a snag. I can't find anything
in the docs to describe
I've already opened a support ticket with MySQL on this issue, but
thought someone here might know the answer, too:
Hi there,
I'm trying to make sure I'm not doing something stupid. I'm trying to
migrate from 4.0 to 4.1, but I'm hitting a snag. I can't find anything
in the docs to describe
I'm running 4.0.16 on a dual-Opteron using the 64bit mysql-max binary
distribution (tar.gz, not rpm) from mysql.com. I have 8GB of RAM, and
it was using about 4.5GB at the time of the crash.
031210 9:24:34 InnoDB: Assertion failure in thread 1171265904 in file
row0upd.c line 713
InnoDB: Fail
;
n_diff = 0;
for (i = 0; i < dtuple_get_n_fields(entry); i++) {
data = rec_get_nth_field(rec, i, &len);
dfield = dtuple_get_nth_field(entry, i);
ut_a(len == dfield_get_len(dfield));
- Original Message -
From: &q
ng utf-8
accent characters, I do not remember who made that bug report.
Please test with 4.0.17 when it comes out.
Thank you,
Heikki
- Alkuperäinen viesti -
Lähettäjä: "Don MacAskill" <[EMAIL PROTECTED]>
Vastaanottaja: "Heikki Tuuri" <[EMAIL PROTECTED]>
I've got an interesting (well, I think so anyway) problem with my
replication.
The slave chugs along just fine, then spits out:
Query caused different errors on master and slave. Error on master:
'Can't execute the query because you have a conflicting read lock'
(1223), Error on slave: 'no erro
I just switched from 4.0.18-max to 4.0.20-max on AMD64 and I'm getting
tons of these in my error log:
040708 2:24:12 Aborted connection 65531 to db: 'db' user: 'user' host:
`10.1.1.27' (Got an error reading communication packets)
When I switch back to 4.0.18-max, they go away.
These are the s
we're just dealing with 1 master/1 slave instead of 1
master/multiple slaves?
Once the old master joins back up, I can let it be a slave for awhile to
catch back up, then swap back, correct?
Thanks in advance!
Don MacAskill
http://onethumb.smugmug.com/
--
MySQL General Mailing List
n advance!
Don
Original Message
Subject: MySQL w/dual-master replication?
Date: Sat, 04 Oct 2003 11:07:43 -0700
From: Don MacAskill <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi there,
I realize it's not supported, but nonetheless, I need to investigate how
possible it is.
-Original Message-
From: Don MacAskill [mailto:[EMAIL PROTECTED]
Sent: Monday 06 October 2003 20:47
To: [EMAIL PROTECTED]
Subject: [Fwd: MySQL w/dual-master replication?]
Hey all,
I sent this a few days ago, but it may have gotten lost in the weekend
for many of you. Don't wo
Hi there,
I've got a bizarre problem I can't seem to solve. I have a small MyISAM
table (6533 rows) with a small FULLTEXT index (3 columns per row, an
average of 1 word per column). When I do an INSERT on the table, many
times the thread gets stuck perpetually in "Query | update". Future
re
+ rows, so it's pretty tiny.
A mysqldump of the table is only 442K.
Has no-one else seen anything like this? I can't imagine I'm the only one.
Thanks,
Don
Don MacAskill wrote:
Hi there,
I've got a bizarre problem I can't seem to solve. I have a small MyISAM
table
This problem is completely repeatable, I'm not the only one having it,
and I've found a (temporary) workaround. I'm not sure if it affects
other machines than AMD64, but it certainly affects them. I've tested
on two now.
If you start MySQL with "skip-concurrent-insert", the problem completely
Success with the bug entry. Nice system, too.
http://bugs.mysql.com/bug.php?id=3483
Thanks,
Don
Don MacAskill wrote:
This problem is completely repeatable, I'm not the only one having it,
and I've found a (temporary) workaround. I'm not sure if it affects
other machines tha
14 matches
Mail list logo
