模拟Mariadb的僵局
我有一个用于从数据库查询数据的应用程序。该应用程序的字段可以放置一个SQL查询,例如:
SELECT number, message FROM test_table WHERE number > ?
我想检查的是该应用程序在僵局中的表现。因此,我的问题是如何模拟僵局,以使选择查询成为僵局受害者?我应该跑什么来实现这一目标?
我正在使用此表:
CREATE TABLE IF NOT EXISTS `test_table` (
`number` int(11) NOT NULL AUTO_INCREMENT,
`time` datetime DEFAULT current_timestamp(),
`message` text DEFAULT NULL,
PRIMARY KEY (`number`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=latin1;
我试图使用这样的两个不同的交易进行僵局,但它们互相僵持,而不是我想要的选择查询:
t1:
START TRANSACTION;
INSERT INTO test_table (message) SELECT 'test'
SLEEP(5);
UPDATE test_table SET message = 'foo';
COMMIT;
t2:
START TRANSACTION;
UPDATE test_table SET message = 'foo';
SLEEP(5);
INSERT INTO test_table (message) SELECT 'test'
COMMIT;
I have an application that I'm using to query data's from the db. This application has a field to put an SQL query like:
SELECT number, message FROM test_table WHERE number > ?
What I want to check, is how this application behave in case of a deadlock. So, my question is how can I simulate a deadlock for the SELECT query to be the deadlock victim? What should I run to make this happen?
I'm using this table:
CREATE TABLE IF NOT EXISTS `test_table` (
`number` int(11) NOT NULL AUTO_INCREMENT,
`time` datetime DEFAULT current_timestamp(),
`message` text DEFAULT NULL,
PRIMARY KEY (`number`)
) ENGINE=InnoDB AUTO_INCREMENT=1 DEFAULT CHARSET=latin1;
I tried to make a deadlock using two different transactions like this, but they were deadlocking each other, not the SELECT query that I wanted:
T1:
START TRANSACTION;
INSERT INTO test_table (message) SELECT 'test'
SLEEP(5);
UPDATE test_table SET message = 'foo';
COMMIT;
T2:
START TRANSACTION;
UPDATE test_table SET message = 'foo';
SLEEP(5);
INSERT INTO test_table (message) SELECT 'test'
COMMIT;
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论