广告
返回顶部
首页 > 资讯 > 数据库 >postgresql lock 锁等待查看
  • 814
分享到

postgresql lock 锁等待查看

postgresqllock锁等待查看 2014-11-24 19:11:34 814人浏览 猪猪侠
摘要

postgresql lock 锁等待查看 当sql请求锁等待超过deadlock_timeout指定的时间时,报类似如下日志: LOG: process xxx1 acquired RowExclusiveLock on relation

postgresql lock 锁等待查看

postgresql lock 等待查看

sql请求锁等待超过deadlock_timeout指定的时间时,报类似如下日志

LOG: process xxx1 acquired RowExclusiveLock on relation xxx2 of database xxx3 after xxx4 ms at xxx
STATEMENT: INSERT ...........

解释: xxx1进程请求位于数据库xxx3中的xxx2对象的RowExclusiveLock锁,已等待xxx4秒。

如何检查或监控锁等待呢?

PostgreSQL提供了两个视图

    1. pg_locks展示锁信息,每一个被锁或者等待锁的对象一条记录。
    1. pg_stat_activity,每个会话一条记录,显示会话状态信息。 我们通过这两个视图可以查看锁,锁等待情况。同时可以了解发生锁冲突的情况。
  • 注意:pg_stat_activity.query反映的是当前正在执行或请求的SQL,而同一个事务中以前已经执行的SQL不能在pg_stat_activity中显示出来。所以如果你发现两个会话发生了冲突,但是他们的pg_stat_activity.query没有冲突的话,那就有可能是他们之间的某个事务之前的SQL获取的锁与另一个事务当前请求的QUERY发生了锁冲突。

通常锁的排查方法如下

    1. 开启审计日志log_statement = "all"
    1. psql 挂一个打印锁等待的窗口(sql语句参考如下)
    1. tail 挂一个日志观测窗口

查看锁等待sql

with
t_wait as
(
select a.mode,a.locktype,a.database,a.relation,a.page,a.tuple,a.classid,a.granted,
a.objid,a.objsubid,a.pid,a.virtualtransaction,a.virtualxid,a.transactionid,a.fastpath,
b.state,b.query,b.xact_start,b.query_start,b.usename,b.datname,b.client_addr,b.client_port,b.application_name
from pg_locks a,pg_stat_activity b where a.pid=b.pid and not a.granted
),
t_run as
(
select a.mode,a.locktype,a.database,a.relation,a.page,a.tuple,a.classid,a.granted,
a.objid,a.objsubid,a.pid,a.virtualtransaction,a.virtualxid,a.transactionid,a.fastpath,
b.state,b.query,b.xact_start,b.query_start,b.usename,b.datname,b.client_addr,b.client_port,b.application_name
from pg_locks a,pg_stat_activity b where a.pid=b.pid and a.granted
),
t_overlap as
(
select r.* from t_wait w join t_run r on
(
r.locktype is not distinct from w.locktype and
r.database is not distinct from w.database and
r.relation is not distinct from w.relation and
r.page is not distinct from w.page and
r.tuple is not distinct from w.tuple and
r.virtualxid is not distinct from w.virtualxid and
r.transactionid is not distinct from w.transactionid and
r.classid is not distinct from w.classid and
r.objid is not distinct from w.objid and
r.objsubid is not distinct from w.objsubid and
r.pid <> w.pid
)
),
t_uNIOnall as
(
select r.* from t_overlap r
union all
select w.* from t_wait w
)
select locktype,datname,relation::reGClass,page,tuple,virtualxid,transactionid::text,classid::regclass,objid,objsubid,
string_agg(
"Pid: "||case when pid is null then "NULL" else pid::text end||chr(10)||
"Lock_Granted: "||case when granted is null then "NULL" else granted::text end||" , Mode: "||case when mode is null then "NULL" else mode::text end||" , FastPath: "||case when fastpath is null then "NULL" else fastpath::text end||" , VirtualTransaction: "||case when virtualtransaction is null then "NULL" else virtualtransaction::text end||" , Session_State: "||case when state is null then "NULL" else state::text end||chr(10)||
"Username: "||case when usename is null then "NULL" else usename::text end||" , Database: "||case when datname is null then "NULL" else datname::text end||" , Client_Addr: "||case when client_addr is null then "NULL" else client_addr::text end||" , Client_Port: "||case when client_port is null then "NULL" else client_port::text end||" , Application_Name: "||case when application_name is null then "NULL" else application_name::text end||chr(10)||
"Xact_Start: "||case when xact_start is null then "NULL" else xact_start::text end||" , Query_Start: "||case when query_start is null then "NULL" else query_start::text end||" , Xact_Elapse: "||case when (now()-xact_start) is null then "NULL" else (now()-xact_start)::text end||" , Query_Elapse: "||case when (now()-query_start) is null then "NULL" else (now()-query_start)::text end||chr(10)||
"SQL (Current SQL in Transaction): "||chr(10)||
case when query is null then "NULL" else query::text end,
chr(10)||"--------"||chr(10)
order by
( case mode
when "INVALID" then 0
when "AccessshareLock" then 1
when "RowShareLock" then 2
when "RowExclusiveLock" then 3
when "ShareUpdateExclusiveLock" then 4
when "ShareLock" then 5
when "ShareRowExclusiveLock" then 6
when "ExclusiveLock" then 7
when "AccessExclusiveLock" then 8
else 0
end ) desc,
(case when granted then 0 else 1 end)
) as lock_conflict
from t_unionall
group by
locktype,datname,relation,page,tuple,virtualxid,transactionid::text,classid,objid,objsubid;

#如果觉得写SQL麻烦,可以将它创建为视图

create view v_locks_monitor as
with
t_wait as
(
select a.mode,a.locktype,a.database,a.relation,a.page,a.tuple,a.classid,a.granted,
a.objid,a.objsubid,a.pid,a.virtualtransaction,a.virtualxid,a.transactionid,a.fastpath,
b.state,b.query,b.xact_start,b.query_start,b.usename,b.datname,b.client_addr,b.client_port,b.application_name
from pg_locks a,pg_stat_activity b where a.pid=b.pid and not a.granted
),
t_run as
(
select a.mode,a.locktype,a.database,a.relation,a.page,a.tuple,a.classid,a.granted,
a.objid,a.objsubid,a.pid,a.virtualtransaction,a.virtualxid,a.transactionid,a.fastpath,
b.state,b.query,b.xact_start,b.query_start,b.usename,b.datname,b.client_addr,b.client_port,b.application_name
from pg_locks a,pg_stat_activity b where a.pid=b.pid and a.granted
),
t_overlap as
(
select r.* from t_wait w join t_run r on
(
r.locktype is not distinct from w.locktype and
r.database is not distinct from w.database and
r.relation is not distinct from w.relation and
r.page is not distinct from w.page and
r.tuple is not distinct from w.tuple and
r.virtualxid is not distinct from w.virtualxid and
r.transactionid is not distinct from w.transactionid and
r.classid is not distinct from w.classid and
r.objid is not distinct from w.objid and
r.objsubid is not distinct from w.objsubid and
r.pid <> w.pid
)
),
t_unionall as
(
select r.* from t_overlap r
union all
select w.* from t_wait w
)
select locktype,datname,relation::regclass,page,tuple,virtualxid,transactionid::text,classid::regclass,objid,objsubid,
string_agg(
"Pid: "||case when pid is null then "NULL" else pid::text end||chr(10)||
"Lock_Granted: "||case when granted is null then "NULL" else granted::text end||" , Mode: "||case when mode is null then "NULL" else mode::text end||" , FastPath: "||case when fastpath is null then "NULL" else fastpath::text end||" , VirtualTransaction: "||case when virtualtransaction is null then "NULL" else virtualtransaction::text end||" , Session_State: "||case when state is null then "NULL" else state::text end||chr(10)||
"Username: "||case when usename is null then "NULL" else usename::text end||" , Database: "||case when datname is null then "NULL" else datname::text end||" , Client_Addr: "||case when client_addr is null then "NULL" else client_addr::text end||" , Client_Port: "||case when client_port is null then "NULL" else client_port::text end||" , Application_Name: "||case when application_name is null then "NULL" else application_name::text end||chr(10)||
"Xact_Start: "||case when xact_start is null then "NULL" else xact_start::text end||" , Query_Start: "||case when query_start is null then "NULL" else query_start::text end||" , Xact_Elapse: "||case when (now()-xact_start) is null then "NULL" else (now()-xact_start)::text end||" , Query_Elapse: "||case when (now()-query_start) is null then "NULL" else (now()-query_start)::text end||chr(10)||
"SQL (Current SQL in Transaction): "||chr(10)||
case when query is null then "NULL" else query::text end,
chr(10)||"--------"||chr(10)
order by
( case mode
when "INVALID" then 0
when "AccessShareLock" then 1
when "RowShareLock" then 2
when "RowExclusiveLock" then 3
when "ShareUpdateExclusiveLock" then 4
when "ShareLock" then 5
when "ShareRowExclusiveLock" then 6
when "ExclusiveLock" then 7
when "AccessExclusiveLock" then 8
else 0
end ) desc,
(case when granted then 0 else 1 end)
) as lock_conflict
from t_unionall
group by
locktype,datname,relation,page,tuple,virtualxid,transactionid::text,classid,objid,objsubid ;

#eg:

create table table_lock(id int primary key, info text);
insert into table_lock values (1,"a");
#session A
begin;
update table_lock set info="aa" where id=1;
select * from table_lock;
#session B
begin;
select * from table_lock;
#session C
begin;
insert into table_lock values (2,"b");
#session D
begin;
truncate table_lock;
waiting......
#or
#ALTER TABLE XXX RENAME TO XXXXX;
#session E
select * from table_lock;
waiting......

#eg:

Pid: 1980
Lock_Granted: false , Mode: AccessExclusiveLock , FastPath: false , VirtualTransaction: 9/4 , Session_State: active
Username: test , Database: postgres , Client_Addr: NULL , Client_Port: -1 , Application_Name: psql
Xact_Start: 2019-02-11 15:35:33.054468+08 , Query_Start: 2019-02-11 15:35:34.283192+08 , Xact_Elapse: 00:01:18.422846 , Query_Elapse: 00:01:17.194122
SQL (Current SQL in Transaction):
truncate table_lock;
--------
Pid: 1894
Lock_Granted: true , Mode: RowExclusiveLock , FastPath: false , VirtualTransaction: 5/128 , Session_State: idle in transaction
Username: test , Database: postgres , Client_Addr: NULL , Client_Port: -1 , Application_Name: psql
Xact_Start: 2019-02-11 15:17:48.342793+08 , Query_Start: 2019-02-11 15:17:48.344543+08 , Xact_Elapse: 00:19:03.134521 , Query_Elapse: 00:19:03.132771
SQL (Current SQL in Transaction):
insert into table_lock values (2,"b");
--------
    1. 前面的锁查询SQL,已经清晰的显示了每一个发生了锁等待的对象,Lock_Granted: true阻塞了Lock_Granted: false
    1. 同时按锁的大小排序,第一行的锁最大(Mode: AccessExclusiveLock级别最高)

处理方法

  • 确认会话状态 查看状态可用以下语句
select pid, state from pg_stat_activity;
# 查看当前会话的pid
highGo=# select pg_backend_pid();
#idle in transaction状态

or

如果他们想手动或定时杀idle的会话,可以用这个语句

SELECT pg_terminate_backend(pid)
FROM pg_stat_activity
WHERE
pid <> pg_backend_pid()
AND state in ("idle", "idle in transaction", "idle in transaction (aborted)", "disabled")
AND state_change < current_timestamp - INTERVAL "15" MINUTE;
  • 注意会话的类型state in ("idle", "idle in transaction", "idle in transaction (aborted)", "disabled")

state text Current overall state of this backend. Possible values are: active: The backend is executing a query. idle: The backend is waiting for a new client command. idle in transaction: The backend is in a transaction, but is not currently executing a query. idle in transaction (aborted): This state is similar to idle in transaction, except one of the statements in the transaction caused an error. fastpath function call: The backend is executing a fast-path function. disabled: This state is reported if track_activities is disabled in this backend.

要快速解出这种状态,terminate最大的锁对应的PID即可。

select pg_terminate_backend(2066);
postgres=# select pg_terminate_backend(1980);
-[ RECORD 1 ]--------+--
pg_terminate_backend | t
  • 注意:此处不要使用操作系统命令kill -9,其会造成所有活动进程被终止,数据库重启。
您可能感兴趣的文档:

--结束END--

本文标题: postgresql lock 锁等待查看

本文链接: https://www.lsjlt.com/news/5725.html(转载时请注明来源链接)

有问题或投稿请发送至: 邮箱/279061341@qq.com    QQ/279061341

本篇文章演示代码以及资料文档资料下载

下载Word文档到电脑,方便收藏和打印~

下载Word文档
猜你喜欢
  • postgresql lock 锁等待查看
    postgresql lock 锁等待查看 当SQL请求锁等待超过deadlock_timeout指定的时间时,报类似如下日志: LOG: process xxx1 acquired RowExclusiveLock on relation...
    99+
    2014-11-24
    postgresql lock 锁等待查看
  • PostgreSQL中的死锁和锁等待
      开始之前明确一下死锁和锁等待这两个事件的异同相同的之处:两者都是当前事物在试图请求被其他事物已经占用的锁,从而造成当前事物无法执行的现象不同的之处:死锁是相关session双方或者多方中必然要牺牲(回滚)至少一个事务,否则双方...
    99+
    2021-09-17
    PostgreSQL中的死锁和锁等待
  • 如何查看MySQL锁等待的原因
    这篇文章给大家分享的是有关如何查看MySQL锁等待的原因的内容。小编觉得挺实用的,因此分享给大家做个参考,一起跟随小编过来看看吧。--sys库的介绍    mysql...
    99+
    2022-10-18
  • mysql InnoDB锁等待的查看以及分析
    本篇内容主要讲解“mysql InnoDB锁等待的查看以及分析”,感兴趣的朋友不妨来看看。本文介绍的方法操作简单快捷,实用性强。下面就让小编来带大家学习“mysql InnoDB锁等待的查看以及分析”吧!在...
    99+
    2022-10-18
  • LOCK中如何实现模拟锁等待现象
    这篇文章主要介绍了LOCK中如何实现模拟锁等待现象,具有一定借鉴价值,感兴趣的朋友可以参考下,希望大家阅读完这篇文章之后大有收获,下面让小编带着大家一起了解一下。1.模拟“锁等待”现象1)开启一个终端创建测...
    99+
    2022-10-19
  • mysql锁等待查询分析
    mysql锁等待分析 1、简单说明 使用innodb存储引擎后,mysql有三张表来分析锁及阻塞的问题,在information_schema下面有三张表:INNODB_TRX、INNODB_LO...
    99+
    2022-10-18
  • Mysql事物锁等待超时Lock wait timeout exceeded;怎么办
    小编给大家分享一下Mysql事物锁等待超时Lock wait timeout exceeded;怎么办,希望大家阅读完这篇文章之后都有所收获,下面让我们一起去探讨吧!问题场景问题出现环境:1、在同一事务内先后对...
    99+
    2023-06-29
  • Lock wait timeout exceeded - 如何解决MySQL报错:锁等待超时
    摘要:在使用MySQL数据库时,有时会遇到锁等待超时的问题。这个问题通常发生在多个事务同时尝试修改同一行数据时,其中一个事务会等待另一个事务的锁释放。本文将介绍如何解决MySQL报错中的锁等待超时问题,并提供具体的代码示例。一、什么是锁等待...
    99+
    2023-10-21
    MySQL 超时 锁等待
  • Lock wait timeout exceeded; try restarting transaction - 如何解决MySQL报错:锁等待超时,尝试重新启动事务
    正文:MySQL作为一种常用的关系型数据库管理系统,被广泛应用于各种类型的应用程序。然而,在使用MySQL时,我们可能会遇到各种错误和异常。其中一个常见的错误是“Lock wait timeout exceeded; try restart...
    99+
    2023-10-21
    MySQL 报错 锁等待超时
  • Mysql查询正在执行的事务以及等待锁的操作方式
    使用navicat测试学习: 首先使用set autocommit = 0;(取消自动提交,则当执行语句commit或者rollback执行提交事务或者回滚) 在打开一个执行update 查...
    99+
    2022-10-18
  • 数据库中如何查看历史会话等待事件对应的session信息
    小编给大家分享一下数据库中如何查看历史会话等待事件对应的session信息,希望大家阅读完这篇文章之后都有所收获,下面让我们一起去探讨吧!此处以enq: TX - row lock contention等待...
    99+
    2022-10-18
  • 数据库中如何查看故障时间等待事件、问题sql及会话访问次数
    这篇文章主要介绍了数据库中如何查看故障时间等待事件、问题sql及会话访问次数,具有一定借鉴价值,感兴趣的朋友可以参考下,希望大家阅读完这篇文章之后大有收获,下面让小编带着大家一起了解一下。DBA_HIST_...
    99+
    2022-10-18
软考高级职称资格查询
编程网,编程工程师的家园,是目前国内优秀的开源技术社区之一,形成了由开源软件库、代码分享、资讯、协作翻译、讨论区和博客等几大频道内容,为IT开发者提供了一个发现、使用、并交流开源技术的平台。
  • 官方手机版

  • 微信公众号

  • 商务合作