PostgreSQL hangs while executing DDL without log message -
i have postgresql-9.2.10 on centos.
i experience following error:
detail: multiple failures --- write error might permanent. error: not open file "pg_tblspc / 143862353 / pg_9.2_201204301 / 16439 / 199534370_fsm": no such file or directory
this happens since stopped postgresql service, ran pg_resetxlog
, started service. logs in pg_log
good, , service listed without problem.
dml works , not ddl statement create table
, otherwise error message thrown or nothing visible in logs in pg_log
.
if try create table, there no reaction, , looks statement blocked lock.
so tried following query locks:
select blocked_locks.pid blocked_pid, blocked_activity.usename blocked_user, blocking_locks.pid blocking_pid, blocking_activity.usename blocking_user, blocked_activity.query blocked_statement, blocking_activity.query blocking_statement 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 , blocking_locks.database not distinct blocked_locks.database , blocking_locks.relation not distinct blocked_locks.relation , blocking_locks.page not distinct blocked_locks.page , blocking_locks.tuple not distinct blocked_locks.tuple , blocking_locks.virtualxid not distinct blocked_locks.virtualxid , blocking_locks.transactionid not distinct blocked_locks.transactionid , blocking_locks.classid not distinct blocked_locks.classid , blocking_locks.objid not distinct blocked_locks.objid , blocking_locks.objsubid not distinct blocked_locks.objsubid , blocking_locks.pid != blocked_locks.pid join pg_catalog.pg_stat_activity blocking_activity on blocking_activity.pid = blocking_locks.pid not blocked_locks.granted;
you corrupted postgresql cluster pg_resetxlog
. how did run command?
i restore last backup.
Comments
Post a Comment