Since upgrading my Solaris9 server to MySQL 4.1.9 (previously 4.1.3),
remote connections to it from my WinXP laptop have become very slow.
Remote connections using the mysql command-line tool (4.1.7 client),
MySQL Query Browser (1.1.5) or JDBC connections with Connector/J
(3.0.16) used to all c
We am having constant index corruption problems since moving
from 4.0.17 to 4.1.3. All tables are InnoDB and we're using
the file-per-table setting on Solaris9.
Every couple days another few tables will show up corrupt
and queries start missing things. The database has never
gone down, there hav
I have some large tables (hundreds of millions of rows) that are extremely
active. They have heavy read and heavy modify activity. But, all
modifications are only on recent records (data added within the last month
is very volatile, but data earlier than that never changes).
We use the InnoDB en
om)
a staging area while the tables were checking. It may come down to
that, but it's certainly not a picture I like.
Thanks -keith
>At 01:21 AM 8/1/2004, Keith Thompson wrote:
>>Thanks Mike,
>>
>>I've always ignored CHECK TABLE because I always thought it was
>>ju
Hi Sergei,
I did come from 4.0.17 to 4.1.3 with a complete dump/reload.
Then, all changes after that forward came via replication.
I didn't read anything about corruption problems as a replication
slave.
-keith
>Hi!
>On Aug 01, Keith Thompson wrote:
>> Thanks Mike,
>>
Thanks Mike,
I've always ignored CHECK TABLE because I always thought it was
just for MyISAM.
I ran CHECK TABLE. It told me that my table was corrupt. I then
dumped the table with mysqldump and recreated it. After that
CHECK TABLE said it was OK (and in comparing values with the master
server
Hi Marc,
Thanks for you response. In answer to your questions, there are no
embedded newlines and I did look at index issues. I did not try
rebuilding the index, which would be easy to do in this case since
the tables are small (unlike a couple of my other tables that have
125+ million rows and
I just discovered that two of my tables (out of about 300)
show a very unusual behavior. This is that "select count(*) ..."
and selecting all the rows and counting them do not produce
the same number.
This is on MySQL 4.1.3 on Solaris9. Look at this:
$ mysql -e "select count(*) from pstat.plist
with username/host/whatever>
>I believe this was because I was trying to connect to MySQL 4.1.x with
>a 4.0.x client. I don't know if that's your case as well.
>http://dev.mysql.com/doc/mysql/en/Old_client.html
>Wes
>On Jul 28, 2004, at 6:21 PM, Keith Thompson wrote
I have a mysql connection problem that I'm trying to understand.
The three servers and the version of mysql they are running (all under
Solaris9) are:
db1 - 4.0.16
db2 - 4.0.17
db3 - 4.1.3
All three systems have the same mysql user and passwords setup. I'll
use the mythical user "xx" with
Is there a limit on what innodb_buffer_pool_size can be set in 4.0.17
(64-bit Solaris 9)?
I tried setting it to 4G in my.cnf and SHOW VARIABLES says it's 0.
-keith
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PR
Is there a limit on what innodb_buffer_pool_size can be set in 4.0.17
(64-bit Solaris 9)?
I tried setting it to 4G in my.cnf and SHOW VARIABLES says it's 0.
-keith
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PR
All of my tables are now InnoDB only. So, what I'd like to do is
reduce MySQL tunable variables down as much as possible for things
that don't affect InnoDB so that I'm not wasting memory on buffers
that will get little or no use.
It's obvious which variables are only for InnoDB (they start with
Given these two tables:
create table t1 (
id int unsigned auto_increment,
a int,
... [other fields]
primary key (id),
index aid (a,id)
) type=innodb;
create table t2 (
id int unsigned,
b int,
... [other fields]
index id (i
What is the preferred way of storing a dollar amount in the range
0.00 - 9.99?
double
decimal(11,2)
bigint (storing value*100)
...?
I'm more interested in speed of use as an indexed column (especially
for range searches) than in disk space usage.
-keith
--
MySQL General
Can I just do a clean shutdown of MySQL, change my configured
innodb_log_file_size, then restart? Or is there more I need
to do to make sure the current log files are flushed to the
data files before changing their size?
Thanks -keith
--
MySQL General Mailing List
For list archives: http://li
I've got a query that's not using an index and I don't understand why.
Here's a stripped down version of what the tables look like:
create table t1 (
id int(10) unsigned not null auto_increment,
x1 date not null,
... 8 other small, fixed fields
primary key (id),
key search_x1 (x1)
)
I have a Java application that is connecting to a MySQL database
via JDBC (Connector/J 3.0.10 connecting to MySQL 4.0.17 server).
I would like to implement a time-limit on certain queries (all
SELECTs) and kill the query if it exceeds a given limit. Is there
a convenient way to do this?
Maybe the
I just had a script fail unexpectedly and now I've got a couple
hundred thousand undo entries rolling back. Yes, I realize that
I should be committing smaller groups--my bad.
I was really hoping to restart my server tonight to change some
server parameters, but a rollback like this will take many
n disable it (ALTER
>> TABLE x DISABLE KEYS), then add data and, on the end, re-enable keys
>> (ALTER TABLE x DISABLE KEYS).
>> mirza
>>
>> Keith Thompson wrote:
>> > Hello all,
>> >
>> > I need to load a new InnoDB table with about 80 milli
Hello all,
I need to load a new InnoDB table with about 80 million rows.
With MyISAM I have often found that it is faster to create
the table without indexes, add all the data, then add the
indexes. Is this true with InnoDB as well, or should I put
my indexes in before loading?
Similarly, I have
I forgot to mention too that this is the 64bit MySQL 4.0.17
running on Solaris9.
>Hi all,
>I decided I needed another index in an InnoDB table that has about
>25 million rows (each 80 bytes long). As I've done dozens of times
>with MyISAM tables, I did a simple "alter table":
> alter table
Hi all,
I decided I needed another index in an InnoDB table that has about
25 million rows (each 80 bytes long). As I've done dozens of times
with MyISAM tables, I did a simple "alter table":
alter table WMH_CHK_a add key JoinTrans (TransID)
This has been running for 14 hours and I have
23 matches
Mail list logo
