Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/node.js/39.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Node.js 原始PostgreSQL查询在使用TypeOrm执行时挂起_Node.js_Postgresql_Sql Update_Typeorm - Fatal编程技术网

Node.js 原始PostgreSQL查询在使用TypeOrm执行时挂起

Node.js 原始PostgreSQL查询在使用TypeOrm执行时挂起,node.js,postgresql,sql-update,typeorm,Node.js,Postgresql,Sql Update,Typeorm,我正在进行此更新查询: 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."

我正在进行此更新查询:

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客户机中执行了相同的查询,它也不会终止。在一次故障排除会话后,我们发现查询被锁定,因为另一个连接正在尝试更新相关资源(在
users
表中的记录,带有来自
user\u images\u image
的外键)以相同的方法用于不同的事务,都在等待提交结果

通过使用相同的连接,我们最终得到了正确的行为

我们通过使用锁监视查询发现:


pg\u stat\u activity
在说什么?连接的状态是什么?@GustavoKawamoto
pg\u stat\u activity
说它是一个锁,即
wait\u event\u type
是锁,
wait\u event
是事务ID,
state
是活动的。这就是你要问的连接状态吗?是的。从外观上看当然,有什么东西会以某种方式锁定你的更新。你可以通过使用找到什么东西锁定了什么。@GustavoKawamoto哦,谢谢你,我会检查它们的。但是,由于我刚刚设法发现它与我正在进行的交易有关,更准确地说,我重写了相同的方法,但没有进行交易,它是有效的…@GustavoKawamoto您对transactionid可能是什么有什么想法吗?我不太清楚它在低级别上是如何工作的。
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;