On Oct 9, 2006, at 7:15 AM, Ow Mun Heng wrote:
Hi All,
Just wanted to know if it would be faster/better to implement this
option into my.cnf
innodb_file_per_table = 1
which would essentially make each table a file on it's own rather than
have it all in 1 file.
My belief is that it would be
Hi! Essentially this is true. However let me qualify that a little...
Clearly to take advantage of 64 to you'll want to change your memory
settings and allocate something in my.cnf over 2G. Also you'll want
to be using OS X 10.4.n, 10.3 and earlier don't really support 64
bit. Now that the
I would expect this to finally be something on the client end,
rather than the server end... is there a search index that gets
rebuilt periodically? Maybe some reports that get generated against
the data? The last example that comes to my mind is if you use a
client that caches data, does
On Sep 28, 2005, at 5:21 PM, Devananda wrote:
Jeff wrote:
Lots of stuff goes in here...
So without going into specifics here... your sort_buffer and
read_buffer become pretty much unimportant if you move everything to
InnoDB... keeping in mind the earlier advice to leave the mysql
On OSX server there is a copy of MySQL already installed and just
installing the MySQL binary doesn't necessarily bypass it. Try
logging on as root with no password, you may still be booting from
Apple's data directory rather than MySQL's... starting mysqld using /
You will need to make sure you have innodb configured in the my.cnf
file and you have enough space built for it in the shared table
space. InnoDB also needs it's own memory pool, so make sure you give
it enough memory. For day to day issues there is no problem doing
innodb/myisam
On Sep 21, 2005, at 5:23 AM, Jeff wrote:
I am interested in how you go about doing a delayed replication to
protect against operator error. We've already fallen victim to that
situation here.
The long story short is we use the fact that MySQL has the ability to
run the SQL thread and the
On Sep 22, 2005, at 11:46 AM, Jeff wrote:
True, is there a way to tell a slave to not replicate certain queries
like alter table or would I need to get creative and stop replication
and all writes to the main database, then issue the alter table
statement, then restart replication with a set
On Sep 16, 2005, at 11:07 AM, Jeff wrote:
There shouldn't be a problem if:
server A is ver 4.0.x
server B is ver 4.1.x
should there?
There will totally by a problem here... The 4.1 server will take the
4.0 feed without issue. The 4.1 server however puts all sorts of
information into
For high volume discussion board type work InnoDB is faster. Our
slow query log droped 66% just by switching engine types.
Earlier comments about innoDB not supporting full text are actually
supposed to read InnoDB doesn't support full text indexes... This is
only important if you really
One of our engineers first installed MySQL on one of our Sun boxes
which was doing nothing more than MySQL... It seems we also put it on
the server and turned it on... it behaved very badly. Essentially
when we started to investigate MySQL and find out if we could use it
we discovered that
of memory to get at,
also no problem.
And of course until it is worked out, stay within the limis of 32 bit
and you don't have a problem :-)
Best Regards, Bruce
On Sep 7, 2005, at 8:51 PM, Scott Haneda wrote:
on 9/7/05 8:42 PM, Bruce Dembecki at [EMAIL PROTECTED] wrote:
Yeah, 64 bit isn't
On Sep 6, 2005, at 11:09 PM, Scott Haneda wrote:
After reading this:
http://www.anandtech.com/mac/showdoc.aspx?i=2436 I suspect OS X
is just
not going to cut it.
So while I think it is beneficial to be open to new things at all
times, there are as always two sides to any story. The
, Scott Haneda wrote:
on 9/7/05 2:40 PM, Bruce Dembecki at [EMAIL PROTECTED] wrote:
We're happy with our Mac based MySQL servers in many respects. We've
got some 64 bit issues that are causing a little grief, so we're
looking at our options... Obviously working with Apple and MySQL to
determine
of memory, it's not an issue to start with.
Best Regards, Bruce
On Sep 7, 2005, at 4:23 PM, Scott Haneda wrote:
on 9/7/05 2:40 PM, Bruce Dembecki at [EMAIL PROTECTED] wrote:
We're happy with our Mac based MySQL servers in many respects. We've
got some 64 bit issues that are causing
We see that error when we go above the memory limits of a 32 bit
operating system. When we run a 64 bit binary on our 64 bit hardware
we can allocate more memory and it fires up fine.
I'm a Mac guy so your string of letters and numbers describing your
hardware and MySQL version don't mean
On Aug 23, 2005, at 10:20 AM, Sunil Vishwas wrote:
I was looking into the storage requirement for the various data types
and
got confused by following comment:
'For the CHAR, VARCHAR, and TEXT types, L and M in the preceding table
should be interpreted as number of bytes before MySQL 4.1 and
Once you decide to use mysqldump, be aware that the quickest way to
export/import large files is to use the --tab feature on export and
mysqlimport to load the data...
Essentially:
On the old (4.0) server:
mysqldump --tab=/var/tmp/directory mydatabase
On the new (4.1) server (assuming you
On Aug 15, 2005, at 5:07 AM, Logan, David (SST - Adelaide) wrote:
Hi Gary,
If you are running unix (or variants thereof), you can go to the
data directory and remove it at the operating system level if the
mysql client can't do it. Not sure about windows though but I would
think the
Still no answer, perhaps, but ther'es still no question.
Per my earlier response... What version of MySQL is the old version
you refer to, what version is the new version you refer to? With that
information someone here is more likely to be able to tell you
something useful... without that
Need more information... what exactly is Our older version, and
what exactly is the newest version of MySql, without this it's hard
to know what issues you may be facing... I imagine you are on 4.0.n
for the old and 4.1.n for the new... but we can't really tell from
the information you
You *COULD* include the information in the my.cnf file under the
[client] area, something like this:
[client]
user=bruce
password=brucesPassword
That would tell the client to use that unless something else is
disabled.
Of course that needs to be saved in plain text in a plain text file
On Jul 26, 2005, at 3:56 AM, Marvin Wright wrote:
Regarding the file size issue, we are on a 32-bit system running
redhat AS3,
we already have idb files in excess of 21Gb, I'm not sure what the
limit is
though if any ?
No, typically a 32 bit file system would have limits like 2G or
On Jul 25, 2005, at 5:33 AM, Marvin Wright wrote:
Hi,
Thanks for your reply.
I've only just moved all tables to there own table space so that I
can put
certain databases on different disks.
Right now my shared tablespace does not hold any databases.
I'm aware that I still need the shared
On Jul 25, 2005, at 1:23 PM, Sujay Koduri wrote:
I guess anywhere we have 3 levels of hierarchies for a phone number.
(Country code, Area code and the actual number).
The advantage of seperating them into different columns(Either an
integer or
a string) is that he can group different phone
On Jul 25, 2005, at 3:47 PM, Chris Kantarjiev wrote:
link_id is indexed. There are about 8 million rows in the table,
and most of them have link_id = null right now. latitude and longitude
are not indexed - but my understanding is that mySQL will only
use one index, and link_id is the
So it appears I am having an issue with 4.1.13 which I'm guessing is
a bug... wanted some input before I file it...
Setting up a new machine to take over for an old one, so it's clean,
Operating System and some empty disks... the server does nothing
other than MySQL so there are no other
I would really like to hear how some of you are handling backups on
high-availability servers. The DBA in my company is skeptical about
switching from MSSQL Server to MySQL, this is one of his reasons
(backups). If someone is making MySQL work in a high-availabity
environment, let's hear about
Hi,
I've just converted my databases so they are using per_table
tablespaces.
When I do a show table status in that database the Comment line
still shows
the amount free, but I assume this doesn't mean anything now ?? It
doesn't
make sense ?
As innodb_file_per_table makes individual
hi,
we've got an old mysql-3.23.58 and a new mysql-4.1.10a and we'de
like to
migrate our data, but it doesn't seems to be so easy:-(
out old server has a latin2 database. after we dump it and try tp
import
into the new ones we always got errors or the spical accented
hungarian
characters
On 7/15/05, Bruce Dembecki [EMAIL PROTECTED] wrote:
This process has worked for us taking our latin1 4.0 databases and
turning them into utf8 4.1 databases. UTF8 data we had already
put in
our 4.0 database despite it's latin1 encoding was correctly exported
out of 4.0 and correctly
Dear All,
Am planning on making MySQL write its data files to disk1 and log
files
to disk2.
My questions are :
1. I know I can put the connections, slow, query, and InnoDB logs on
disk2.
Is it also possible (and advisable) to put the binary logs with
them
?
We log to the OS Disk,
On 7/15/05, Bruce Dembecki [EMAIL PROTECTED] wrote:
This process has worked for us taking our latin1 4.0 databases and
turning them into utf8 4.1 databases. UTF8 data we had already
put in
our 4.0 database despite it's latin1 encoding was correctly exported
out of 4.0 and correctly
I've got some years-old MySQL databases mostly in 4.0, but one server
running 3.23 that are all using the default encoding.
I want to update all their data to 4.1 with UTF-8 encoding.
Anyone done this kind of dump-and-update?Any advice to share or
good URLs you've seen with others' advice
Good issue, I totally had the same concerns, so we built our own
system. As a side note we run an admin server which we use to
generate reports, run backups and so on - it takes load off the
production servers, where speed is critical. Recovery from backup
however is a whole other issue,
does MySQL have a pretty way to persist snapshots of various show
commands?
for example in Oracle you could just do:
insert into sysstat_log select sysdate, * from v$sysstat;
--(an ugly, overly simple example)
can the show commands be called/parsed with DBD/DBI?
so far the only way I've
Just to make things REALLY messy... try setting the default character
set of a 4.1 server to utf8, and then importing your data from 4.0...
your mysql usernames are in real trouble now, because utf8 considers
itself to be multi byte and takes more space, cutting down on the 16
characters
So I am attempting a 5.0 upgrade from 4.1 on one of our OS X servers...
When attempting to launch mysqld it quits, with this error (showing
two from the log files, happens with our build or the MySQL binary):
050617 14:03:46 mysqld started
Hi! Can anyone help me with a 64 Bit OS X 10.4 binary? I've tried to compile
it myself but get errors in the make process that I have no idea what to
do with.
Apple ships a MySQL 4.1.10a binary with Tiger, but it's not 64 bit. MySQL
doesn't have a 64 Bit OS X 10.4 binary yet.
Maybe my question
We have a large OS X MySQL deployment on multiple servers and we have
experienced a range of weirdness with table corruption that I was never able
to fully determine the cause for.
Moving to G5 Xserves (from G5 Towers and G4 Xserves) has seen all the
problems go away as if a switch were thrown. I
I have successfully configured mysqld_multi to have mysql 4.1.11 and
5.0.3 beta running on the same machine:
I would like to see how you configured mysqld_multi to do that, if you could
send me the information off list I'd appreciate it.
# mysqld_multi start
# exit
% mysqld_multi report
Looking at your my.cnf files I don't see where you've told the slave what
server to connect to. The slave needs to know what server is the master.
This is usually accomplished by including a couple of lines in my.cnf.
If the file master.info is in the data directory it will override the my.cnf
Hannes Rohde [EMAIL PROTECTED] wrote:
innodb_data_file_path=ibdata1:2G:autoextend
innodb_buffer_pool_size=1200M
innodb_additional_mem_pool_size=20M
May not solve the replication issue, but if this is a 4GByte server that is
dedicated to MySQL (ie you aren't using memory for anything
Hannes Rohde [EMAIL PROTECTED] wrote:
innodb_data_file_path=ibdata1:2G:autoextend
innodb_buffer_pool_size=1200M
innodb_additional_mem_pool_size=20M
May not solve the replication issue, but if this is a 4GByte server that is
dedicated to MySQL (ie you aren't using memory for anything
Hi! We have a problem converting our 4.0 text columns from a Hong Kong
database to 4.1. In order to get the conversions to work generally speaking
we build our databases with default character set utf8 - it means the German
products still work, and the English ones, and the Chinese ones, and
So today for the second time in six weeks we are faced with rolling back to
mysql 4.0 because of dramas with character sets. I don't know about anyone
else but this supposedly wonderful feature has been nothing but a nightmare
for us.
So our Application servers use Unicode for our non US English
PROTECTED] wrote:
Hi Bruce
SNIP
- Original Message -
From: Bruce Dembecki [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Thursday, December 30, 2004 2:51 AM
Subject: Re: Fixing the worst InnoDB corruption bug in 3 years -
when
As a side note with demonstrated performance
Hi Scott! We use MySQL on 9 Mac OS X machines. While we are looking at
moving some of that back to big Sun boxes, that's a memory access/64 bit
issue, not (directly) a performance issue.
Looking at the live stats one of the machines has an uptime of 55 days and
has averaged 405.78 queries per
Hi! We're setting up a Solaris system which is behaving poorly, very slow
disk performance. The nice folks at Sun have suggested a mismatch between
the block size MySQL is writing to disk and the block size the the Operating
System is writing to disk.
While we can see the logic in the argument, I
. Fortunately, the bug affects few users, because not too many
are running with innodb_file_per_table.
Regards,
Heikki
On 12/28/04 2:38 PM, Bruce Dembecki [EMAIL PROTECTED] wrote:
In the MySQL Manual under InnoDB in the Using Per-Table Tablespace section
it says clearly at the top
Regards, Bruce
On 12/28/04 1:44 PM, Bruce Dembecki [EMAIL PROTECTED] wrote:
Tucker, Gabriel wrote:
Anil
Write a script that does a slave status and check if either of the threads
are
running. You could
further check for error numbers and descriptions. This is what we do.
Gabe
In the MySQL Manual under InnoDB in the Using Per-Table Tablespace section
it says clearly at the top:
NOTE: CRITICAL BUG in 4.1 if you specify innodb_file_per_table in `my.cnf'!
If you shut down mysqld, then records may disappear from the secondary
indexes of a table. See (Bug #7496) for more
So I have a question for those who understand developer speak and MySQL
builds and so on...
Apple announced their new OS earlier this week, including this information
on the improvements to 64 Bit version using the G5 processor:
http://www.apple.com/macosx/tiger/64bit.html
One of our biggest
I'm not sure of the right way to submit these things, so I'll do it here...
I want to dump some data form the binlogs and process it back into the
servers. However I just want to process the data from one specific server.
In mysqlbindump I can optionally specifiy a specific database for the
There seems to be some issues we are experiencing with this new
lower_case_table_names variable introduced in 4.0.17 and modified in 4.0.18.
So much so that I can't upgrade to 4.0.18 at all.
Here is the startup log from a 4.0.18 mysqld:
040227 02:00:22 mysqld started
040227 2:00:22 Warning:
Hi! One of my associates here read a report somewhere that mysqld when
compiled under OS X 10.3 was 40%+ more efficient due to improvements in the
compilers and the way 10.3 work. Also 10.3 is a 64 Bit Operating System and
it would be a major benefit to us to set some of the memory values in
Help, I seem to be running into a problem with replication which up until
now has served us well.
We run mysql servers in pairs, with each server in a pair mastering off the
other. So for example mysql1 masters off mysql2, which masters off mysql1.
Friday morning one server stopped accepting
On Jan 28, 2004, at 12:01 PM, Bruce Dembecki wrote this wonderful stuff:
So.. My tips for you:
1) Consider a switch to InnoDB, the performance hit was dramatic, and it's
about SO much more than transactions (which we still don't do)!
Consider it switched! as soon as I find the way to do
I don't think there would be any benefit to using InnoDB, at least not
from a transaction point of view
For the longest time I was reading the books and listening to the experts
and all I was hearing is InnoDB is great because it handles transactions.
Having little interest in transactions per
On 1/28/04 10:29 AM, stairwaymail-mysql at yahoo dot com wrote:
So should we always use InnoDB over BerkeleyBD? I was
under the impression Berkeley was faster and better at
handling transactions.
Dan
Eermm... That's outside my scope of expertise, my experiences have been
exclusively with
);
ut_a(len == dfield_get_len(dfield));
- Original Message -
From: Bruce Dembecki [EMAIL PROTECTED]
Newsgroups: mailing.database.myodbc
Sent: Tuesday, November 25, 2003 7:28 AM
Subject: InnoDB caused crash and left me a log entry...
InnoDB seems to have crashed on us
InnoDB seems to have crashed on us, and put the errors below into the log
files... It took several crashes and some time but I was able to isolate the
extremely simple query involved.
Server is OSX 10.3 running on a Dual 200MHZ G5 with 4Gigs ram. MySQL is
4.0.16.
The original queries to crash
Hi! I'm struggling to understand how to fix the mysqld_safe script for an
OSX machine. If I run mysql.server stop then the mysqld process is killed
and mysqld_safe promptly starts it again. I know mysqld_safe is supposed to
start mysqld if it stops but I also know there are times I need to work on
Hi. We are migrating our Solaris setup to an OSX server. I used InnoDB Hot
Backup to copy the InnoDB files, and copied the .frm files for each of the
databases.
Under OSX I connect top the server and it sees the databases. If I use
some_database where some_database has mixed case table names I
why this
instance was behaving as if it was set to 1.
Best Regards, Bruce
On 9/25/03 11:27 PM, Bruce Dembecki [EMAIL PROTECTED] wrote:
Hi. We are migrating our Solaris setup to an OSX server. I used InnoDB Hot
Backup to copy the InnoDB files, and copied the .frm files for each of the
databases
I thought I had most things figured out for our challenging replication
setup. However this morning we have a failure I can't figure out... Here are
the errors:
030613 5:13:50 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306',
replication started in log 'binary-log.035' at position
66 matches
Mail list logo
