Re: Deleting Records in Big tables

- Original Message - > From: "mos" > > If you could use MyISAM tables then you could use Merge Tables and Ick, merge tables :-) If your version is recent enough (Isn't 4.whatever long out of support anyway?) you're much better off using partitioning - it's engine-agnostic and has a lot

Re: Issue With Subqueries

- Original Message - > From: "Javier Yévenez" > > If the field db1.table1.field1 has the same name that the field > db2.table1.field1, maybe you have to use an alias for each table: No, he's using a subquery, those fields cannot be referenced. -- Bier met grenadyn Is als mosterd by den

Re: Issue With Subqueries

- Original Message - > From: "Shawn Green (MySQL)" > > Simple math (set theory) suggests that all of the values of field1 on > db2.table1 contain only copies or duplicates of the field1 values in > the rows in db1.table1. Shawn, The "select count(distinct)"s show that db1.table1.field1

Re: Restore data from MySQL data files

Hah. I suspect the machine was running when it crashed - that is, the mysql was shut down uncleanly? You can safely ignore the mysql.plugin bit for the moment - that's for when it's booted properly. It looks like the newer InnoDB has trouble reading your ibdata file. Possible causes: * Are all

LOAD DATA INFILE Problem

Hello, after switching from MySQL 5.0.67 to 5.1.59 we get the following problem: We want to import data from a textfile example of the textfile: t...@test.com$yes$432145$xyz The command is: LOAD DATA LOCAL INFILE 'textfile.txt' INTO TABLE TESTTABLE FIELDS TERMINATED BY '$'; Selecting the data

Re: Reusing "ibdata1" space

- Original Message - > From: "Nick Khamis" > > I should mention that we have deleted the ib_* files in the past. I hope that was an accident, because if you thought that was a good idea I'm sending someone over with the spiked cluebat. Luckily for you, the solution to that particular p

Relication Issues

Good morning list, I am having issues with my replication setup. it seems that every few weeks/months something happens, and I have to restart it, skip a row, or delete, rsync and restart replication from scratch. The databases that are being replicated, are rather large... there are about 12 new

Re: Relication Issues

replication is buggy sometimes but without any outputs desribing your problem nobody can really help you - memory tables as example are making much more troubles as myisam Am 10.11.2011 14:26, schrieb Steven Staples: > Good morning list, > > I am having issues with my replication setup. it seems

RE: Relication Issues

My Apologies, The tables are all MyISAM, most of the inserts/updates/deletes are done through stored procedures on the master. There are about 2 stored procedure calls per second, consisting of a whole bunch of queries, updates, and inserts within them. The latest issue(s) we're having, are: Co

Re: Relication Issues

Hi, It could be a hardware issue, as if you do not use RAID and you have bad sectors or the likes. But the most common cause could be a server crash. The INSERT or transaction was partially completed when server crash. When the slave is then restarted, it will try to execute the transaction/statem

Re: Reusing "ibdata1" space

I wonder, if there could be any method to regain InnoDB space other than dump the whole database and reimport. Thanks, On Thu, Nov 10, 2011 at 12:44 AM, Johan De Meersman wrote: > - Original Message - > > From: "Nick Khamis" > > > > I should mention that we have deleted the ib_* files i

Re: Reusing "ibdata1" space

- Original Message - > From: "Prabhat Kumar" > I wonder, if there could be any method to regain InnoDB space other > than dump the whole database and reimport. Very simple answer to that: no. -- Bier met grenadyn Is als mosterd by den wyn Sy die't drinkt, is eene kwezel Hy die't dr

"InnoDB free" - What does it really mean?

In the "show table status" output, there is comment field labeled "InnoDB free". Can someone explain what kind of free space is counted in this figure? Is it space that is not currently part of any segment? Does it include empty pages within segments? Does it include unused space within page

Re: "InnoDB free" - What does it really mean?

Hi, The comment is just telling you how much free space is in your InnoDB datafile(s). When that approaches 0, InnoDB will add the data file. Image that there's a box, say it Innodb tablespace, this box is consist of your data, and innodb free is the same as the (capacity of your box - usage) To

Re: "InnoDB free" - What does it really mean?

it refers to free innodb tablespace. From: "Rozeboom, Kay [DAS]" To: "mysql@lists.mysql.com" Sent: Thursday, November 10, 2011 10:03 AM Subject: "InnoDB free" - What does it really mean? In the "show table status" output, there is comment field labeled "InnoDB