What I do here is:
Back up the production DB.
Restore it on the development server.
Do the development.
When a schema change is needed I write SQL to alter(upgrade) the
development DB to match development needs.
When development is done, restore the production DB to the development
server again.
M
I would like to add a correction.
I have been unable to remove the table lock from the linux install with
these techniques.
> -Original Message-
> From: Power, Paul C. [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 17, 2007 12:24 PM
> To: mysql@lists.mysql.com
>
OnMySQL 5.1.14-beta-community (windows) 5.1.7-beta (linux)
Consider:
CREATE TABLE
Entity
(
Entity_ID char(4) NOT NULL,
Entity_Name varchar(50) NULL,
PRIMARY KEY ( Entity_ID )
) ENGINE=InnoDB ;
now create a dumb function to use this data:
DELIMITER $$
DROP FUNCTION IF EXISTS voxin
Baron-
Thank you for the InnoDB Lock Monitor pointer. I now have a greate deal
of informaiton to digest. I will try innotop when I have a chance.
:)
-Paul
>
> Hi Paul,
>
> Power, Paul C. wrote:
> > I have an INSERT waiting for a table lock, and i do not
Table_Locks_Immediate and Table_Locks_waited.
What does MySQL do exactly to get those values?
Can it be determined what locks had to wait, and why?
-Paul
I have an INSERT waiting for a table lock, and i do not understand why.
---TRANSACTION 0 308691, ACTIVE 5 sec, process no 8876, OS thread id
1296547864 inserting
mysql tables in use 1, locked 1
LOCK WAIT 1 lock struct(s), heap size 320
MySQL thread id 79126, query id 1113322 bil.oneeighty.com 216
