TypeOrm으로 실행하면 원시 PostgreSQL 쿼리가 중단됨
Aug 18 2020
이 업데이트 쿼리를 만들고 있습니다.
await this.userRepository.query(
`
update "user" u
set profile_pic = i.name
from user_images_image uii
inner join image i on uii."imageId" = i."id"
where uii."userId" = u.id and u.id = ${userId} and i.id = ${imageId};
`,
);
그리고 DB 클라이언트에서 동일한 쿼리를 실행해도 종료되지 않고 예상대로 작동합니다.
답변
1 GustavoKawamoto Aug 19 2020 at 01:48
문제 해결 세션 후 다른 연결이 동일한 방법으로 다른 트랜잭션에 대해 관련 리소스 ( users
의 외래 키 가있는 테이블 의 레코드)를 업데이트하려고 시도했기 때문에 쿼리가 잠 겼음을 발견했습니다 user_images_image
. 둘 다 커밋 결과를 기다리고 있습니다. .
동일한 연결을 사용함으로써 우리는 올바른 행동을하게되었습니다.
문서에서 잠금 모니터링 쿼리 를 사용하여 알아 냈습니다 .
SELECT blocked_locks.pid AS blocked_pid,
blocked_activity.usename AS blocked_user,
blocking_locks.pid AS blocking_pid,
blocking_activity.usename AS blocking_user,
blocked_activity.query AS blocked_statement,
blocking_activity.query AS current_statement_in_blocking_process,
blocked_activity.application_name AS blocked_application,
blocking_activity.application_name AS blocking_application
FROM pg_catalog.pg_locks blocked_locks
JOIN pg_catalog.pg_stat_activity blocked_activity ON blocked_activity.pid = blocked_locks.pid
JOIN pg_catalog.pg_locks blocking_locks
ON blocking_locks.locktype = blocked_locks.locktype
AND blocking_locks.DATABASE IS NOT DISTINCT FROM blocked_locks.DATABASE
AND blocking_locks.relation IS NOT DISTINCT FROM blocked_locks.relation
AND blocking_locks.page IS NOT DISTINCT FROM blocked_locks.page
AND blocking_locks.tuple IS NOT DISTINCT FROM blocked_locks.tuple
AND blocking_locks.virtualxid IS NOT DISTINCT FROM blocked_locks.virtualxid
AND blocking_locks.transactionid IS NOT DISTINCT FROM blocked_locks.transactionid
AND blocking_locks.classid IS NOT DISTINCT FROM blocked_locks.classid
AND blocking_locks.objid IS NOT DISTINCT FROM blocked_locks.objid
AND blocking_locks.objsubid IS NOT DISTINCT FROM blocked_locks.objsubid
AND blocking_locks.pid != blocked_locks.pid
JOIN pg_catalog.pg_stat_activity blocking_activity ON blocking_activity.pid = blocking_locks.pid
WHERE NOT blocked_locks.GRANTED;