我的Postgres数据库在某些被审计的表RAW操纵后崩溃
我收到此错误:
内部服务器错误
javax.persistence.optimisticlockexception:org.hibernate.exception.lockacquicitionException:无法提取结果集 ... 由于与恢复冲突而终止连接 详细信息:用户持有关系锁的时间太长。 ... javax.persistence.optimisticlockexception:org.hibernate.exception.lockacquicitionException:无法提取结果集
I get this error:
Internal Server Error
javax.persistence.OptimisticLockException: org.hibernate.exception.LockAcquisitionException: could not extract ResultSet
...
connection was terminated due to conflict with recovery
Detail: User was holding a relation lock for too long.
...
javax.persistence.OptimisticLockException: org.hibernate.exception.LockAcquisitionException: could not extract ResultSet
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
You must have run something like
DROP/ALTER TABLE
,TRUUNCATE
,LOCK
,CLUSTER
and similar commands that require an访问独家
锁定流程复制的表上的表上,或者自动驾驶在那里截断了一个表。这样的锁被复制,并与备用服务器上该表上运行的任何查询发生冲突。一旦max_standby_streaming_delay
被超过,查询将被取消。在这里 是一些背景信息。
You must have run something like
DROP/ALTER TABLE
,TRUUNCATE
,LOCK
,CLUSTER
and similar commands that require anACCESS EXCLUSIVE
lock on the table on the streaming replication primary, or autovacuum truncated a table there. Such a lock is replicated and conflicts with any query running on that table on a standby server. Oncemax_standby_streaming_delay
is exceeded, the query is canceled.Here is some background information.