postgresql集群报错解决(SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 65535))

10月25号之后只能对evap数据库进行select操作,且运行报错如下:

org.postgresql.util.PSQLException: ERROR: pooler: failed to create connections in parallel mode for thread 140705041217280 在位置:SQL statement "EXECUTE DIRECT ON (cn_5002) 'SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 65535)'"

查询用户线权限:
postgresql集群报错解决(SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 65535))
文章图片

查询表权限:
select * from INFORMATION_SCHEMA.role_table_grants where table_catalog='evap' and table_name='z_area_monitor_qygn12' and table_schema='public'; select * from INFORMATION_SCHEMA.role_table_grants where grantee='admin';

postgresql集群报错解决(SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 65535))
文章图片

查看锁,无问题:
postgresql集群报错解决(SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 65535))
文章图片

解决办法:gsql登录时换用66.30,端口不变,操作恢复正常
参考文章:https://sourceforge.net/p/postgres-xc/mailman/message/32086357/
【postgresql集群报错解决(SELECT pg_catalog.pg_try_advisory_xact_lock_shared(65535, 65535))】https://www.oschina.net/translate/postgresql-locking-revealedPostgreSQL 锁解密
https://yq.aliyun.com/ask/184?order=ctimepg中关于AccessShareLock和ExclusiveLock的问题
https://blog.csdn.net/cdnight/article/details/84452012【pg数据库】表锁 行锁 隔离级别及xmin xmax等系统行含义
https://blog.csdn.net/constzl/article/details/79206887AntDB重分布流程记录

    推荐阅读