Lister les verrous actuels

Oracle

SELECT s.sid, s.serial#, l.type, DECODE(l.lmode,0,'None',1,'Null',2,'Row-S',3,'Row-X',4,'Share',5,'S/Row-X',6,'Exclusive') AS lmode, o.object_name, s.username, s.blocking_session
FROM v$lock l
JOIN v$session s ON s.sid = l.sid
LEFT JOIN v$locked_object lo ON lo.session_id = l.sid
LEFT JOIN dba_objects o ON o.object_id = lo.object_id
ORDER BY s.sid;

Affiche les verrous actifs et la session bloquante (blocking_session) via v$lock et v$locked_object.

PostgreSQL

SELECT l.locktype, l.mode, l.granted, a.pid, a.usename, a.state, a.wait_event_type, a.query
FROM pg_locks l
JOIN pg_stat_activity a ON a.pid = l.pid
WHERE l.pid <> pg_backend_pid()
ORDER BY l.granted, a.pid;

Joint pg_locks à pg_stat_activity ; les lignes avec granted=false indiquent des verrous en attente (bloqués).

MySQL

SELECT ENGINE, OBJECT_SCHEMA, OBJECT_NAME, LOCK_TYPE, LOCK_MODE, LOCK_STATUS, THREAD_ID
FROM performance_schema.data_locks;
-- For waiters: SELECT * FROM performance_schema.data_lock_waits;

performance_schema.data_locks liste les verrous InnoDB actuels et data_lock_waits les relations d'attente.

SQL Server

SELECT tl.resource_type, tl.resource_database_id, tl.request_mode, tl.request_status, tl.request_session_id, es.login_name, er.blocking_session_id
FROM sys.dm_tran_locks tl
LEFT JOIN sys.dm_exec_sessions es ON es.session_id = tl.request_session_id
LEFT JOIN sys.dm_exec_requests er ON er.session_id = tl.request_session_id
ORDER BY tl.request_session_id;

sys.dm_tran_locks affiche les demandes de verrou actuelles ; celles avec request_status = WAIT sont des demandes bloquées.

MongoDB

db.currentOp({ "$or": [ { "waitingForLock": true }, { "locks": { "$exists": true } } ] })

db.currentOp affiche les opérations en attente de verrou (waitingForLock) et celles qui détiennent des verrous ; MongoDB verrouille au niveau document/collection, pas au niveau ligne.

Redis

# Not applicable: Redis has no row/table lock concept; commands run sequentially on a single thread. For blocking analysis, use the SLOWLOG and LATENCY commands.

Redis étant mono-thread, il n'y a pas de liste de verrous traditionnelle.

Elasticsearch

GET _cluster/pending_tasks

Elasticsearch n'a pas de verrous de ligne ; ceci liste les tâches de modification du cluster en file d'attente sur le master (pending tasks).