【问题标题】:PostgreSQL hangs while executing DDL without log messagePostgreSQL 在没有日志消息的情况下执行 DDL 时挂起
【发布时间】:2015-07-08 08:50:18
【问题描述】:

我在 CentOS 上有 Postgresql-9.2.10。

我遇到以下错误:

DETAIL: Multiple failures --- write error might be permanent.
ERROR: could not open file "pg_tblspc / 143862353 / PG_9.2_201204301 / 16439 / 199534370_fsm": No such file or directory

发生这种情况是因为我停止了 PostgreSQL 服务,运行 pg_resetxlog 并启动了该服务。 pg_log中的日志看起来不错,服务列出也没有问题。

DML 运行良好,但不是像 CREATE TABLE 这样的 DDL 语句,否则会抛出错误消息或在 pg_log 的日志中看不到任何内容。

如果我尝试创建表,没有反应,看起来语句被锁阻塞了。

所以我尝试了以下查询来查找锁:

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 blocking_statement
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;

【问题讨论】:

  • 该错误似乎与文件系统相关,与锁相关。您是否检查过提到的文件路径是否存在,由 postgres 用户拥有并且具有正确的权限
  • 有没有办法知道postgresql添加pg_log的状态?
  • "create table" 语句只是等待 ppuninde 没有响应,pg_log 但它没有出现在消息中。只有一句话,简直就是创建一个空表。

标签: postgresql ddl


【解决方案1】:

您可能使用pg_resetxlog 破坏了 PostgreSQL 集群。你究竟是如何运行命令的?

我会从上次好的备份中恢复。

【讨论】:

    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2011-05-02
    • 1970-01-01
    • 2016-02-23
    • 1970-01-01
    相关资源
    最近更新 更多