文章目录
- 环境
- 症状
- 问题原因
- 解决方案
环境
系统平台：N/A
版本：4.1.1
症状
使用过程中数据库突然中止，且无法启动，存在一些类似报错信息：
LOG: checkpoints are occurring too frequently (7 seconds apart)
HINT: Consider increasing the configuration parameter “checkpoint_segments”.
PANIC: could not write to file “pg_xlog/xlogtemp.9028”: No space left on device
STATEMENT: insert into t1 select generate_series(1,1000000),‘nan’,md5(‘highgo’);
PANIC: could not write to file “pg_xlog/xlogtemp.9028”: No space left on device
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: LOG: server process (PID 9028) was terminated by signal 6: Aborted
DETAIL: Failed process was running: insert into t1 select * from t2;
LOG: terminating any other active server processes
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
Failed.
!> LOG: all server processes terminated; reinitializing
LOG: database system was interrupted; last known up at 2017-12-04 18:05:09 CST
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/103FE040
LOG: redo done at 0/14FFFF68
LOG: last completed transaction was at log time 2017-12-04 18:05:09.85515+08
PANIC: could not write to file “pg_xlog/xlogtemp.9084”: No space left on device
LOG: startup process (PID 9084) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
LOG: database system shutdown was interrupted; last known up at 2017-12-04 18:05:23 CST
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at 0/103FE040
LOG: redo done at 0/14FFFF68
LOG: last completed transaction was at log time 2017-12-04 18:05:09.85515+08
PANIC: could not write to file “pg_xlog/xlogtemp.9138”: No space left on device
LOG: startup process (PID 9138) was terminated by signal 6: Aborted
LOG: aborting startup due to startup process failure
问题原因
wal日志所在文件系统空间不足。
解决方案
清理该文件系统下过期的临时文件，或将wal日志存放至更大的系统空间中。
注意：严禁删除wal日志！
)
