The query under process ID 180233 looks like it is in distress.
Here is the query itself
SELECT COUNT(DISTINCT A.`campaignid`) INTO _c
FROM `ox_campaigns` A
INNER JOIN `selfserving_users` B ON B.`user_id` = A.`uid`
INNER JOIN `v3_cam_date` C ON C.`campaignid` = A.`campaignid`
WHERE A.`revenue_type` = 5 AND A.`deleted` = 0
AND A.`expire` = DATE_ADD(CURRENT_DATE, INTERVAL 1 DAY)
AND A.`isExpired` = 0
AND IF( NAME_CONST('_permitid',3) = -1, 1=1,
IF( NAME_CONST('_permitid',3) = 0, A.`uid` IN
(SELECT C.`user_id` FROM `selfserving_users` C
WHERE C.`groupid` = NAME_CONST('_groupid',12) ) ,
A.`uid` = NAME_CONST('userid',388)));
The scary part about the query is the self-reference
You have selfserving_users
acting in a self serving manner against itself.
Sometimes, the MySQL Query Optimizer will play a bait-and-switch, smoke-and-mirrors games with data, especially with a self reference, in order to formulate the best EXPLAIN plan possible. While mysql is very capable of completing sub-SELECTs, it can be still be expensive.
However, this is just a symptom that manifested because of Process ID 97. What is really the issue here?
LOAD DATA INFILE against an InnoDB table could make mysqld a little punch drunk. I don't believe (or at least I don't exercise full confidence) you can encapsulate it as a normal transaction although this was addressed back in MySQL 5.0.
Just picture it:
- You are hammering the InnoDB Buffer
- Some memory swapping may be going on
- Possible full table locking issues that are affecting data pages outside the
v3_zone_date
table (such was with the selfserving_users
table)
There may be a way to throttle the LOAD DATA INFILE process on an InnoDB table. I cannot give you a solid answer on this one, but try this link from Baron Schwartz.
UPDATE 2012-02-22 12:00 EST
There is open bug report in MySQL 5.5.7 called Deadlock when DDL under LOCK TABLES WRITE, READ + PREPARE. At the bottom of the report, a person complained about a block problem cause by the explicit LOCK TABLES
.
Launching a COMMIT
on locked rows in a table would hang because of trying to unraveling MVCC data assocaited with the locked rows. Based on the InnoDB Status you have shown, there would exist 6933 row locks on the table you are importing. I know that in Oracle, when introducing new rows to a table, MVCC is still generated because the previous version of the newly inserted row is a nonexistent row. The same must be occurring for InnoDB.
UPDATE 2012-02-22 12:42 EDT
In your question you stated the following about your .NET process
- LOCK TABLES;
- SET autocommit=0;
- SET unique_checks=0;
- SET foreign_key_checks=0;
- LOAD DATA;
- COMMIT;
- UNLOCK TABLES;
- SET autocommit=1;
- SET unique_checks=1;
All of these events are running within the same DB Session. This is also happening within one DB Connection. Thus, this is not a deadlock in the traditional sense. It is just a case of blocking your COMMIT within a given DB Connection/Session because the tables were locked within the same DB Connection/Session.
UPDATE 2012-02-23 19:00 EDT
I would change the sequence to be this:
- SET autocommit=0;
- SET unique_checks=0;
- SET foreign_key_checks=0;
- LOCK TABLES;
- LOAD DATA;
- UNLOCK TABLES;
- COMMIT;
- SET autocommit=1;
- SET unique_checks=1;
- SET foreign_key_checks=1;
Please remember, a COMMIT
cannot proceed if you have the tables locked in serial fashion. Therefore, UNLOCK TABLES
must precede COMMIT
.
I don't think you can do it the way you are trying to... if my understanding of "A pseudo-type cannot be used as a column data type" is correct.
However, you can do something similar.
First, you define your composite type (for instance, we have a "point in two dimensions", with fields x
and y
):
-- Need to define the composite type
CREATE TYPE point_2d AS
(
x real,
y real
) ;
Then, you can write 'literals' that need to be cast to point_2d
so that PostgreSQL know which exact type they have. So, this works:
CREATE TABLE
ttt AS
SELECT
*
FROM
(
VALUES
('(1.5, 2.5)'::point_2d, '(-1.3, -2.2)'::point_2d),
('(2.3, 4.4)'::point_2d, '(-2.2, -3.3)'::point_2d)
) AS lines (start_point, end_point) ;
And then, you can perform queries like:
SELECT
(start_point).x AS x_start,
(start_point).y AS y_start,
(end_point).x AS x_end,
(end_point).y AS y_end
FROM
ttt ;
Best Answer
There is generally no exclusive locking in Azure SQL Data Warehouse as the default isolation level is
READ UNCOMMITTED
as documented here.Other approaches to this such as
sp_get_applock
are also unavailable. Therefore you manage this based on low concurrency and workflow, ie don't allow users to connect to your warehouse during the update, or use some kind of flag that has to be checked during operations.