postgresql意外中止,无法启动
来源:互联网 发布:mac画图板 编辑:程序博客网 时间:2024/05/16 17:14
PG数据库在使用过程中数据库突然中止,且无法启动,存在一些类似报错信息:
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 deviceSTATEMENT: 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 deviceserver closed the connection unexpectedlyThis probably means the server terminated abnormallybefore or while processing the request.The connection to the server was lost. Attempting reset: LOG: server process (PID 9028) was terminated by signal 6: AbortedDETAIL: Failed process was running: insert into t1 select * from t2;LOG: terminating any other active server processesWARNING: terminating connection because of crash of another server processDETAIL: 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; reinitializingLOG: database system was interrupted; last known up at 2017-12-04 18:05:09 CSTLOG: database system was not properly shut down; automatic recovery in progressLOG: redo starts at 0/103FE040LOG: redo done at 0/14FFFF68LOG: last completed transaction was at log time 2017-12-04 18:05:09.85515+08PANIC: could not write to file "pg_xlog/xlogtemp.9084": No space left on deviceLOG: startup process (PID 9084) was terminated by signal 6: AbortedLOG: aborting startup due to startup process failure--------------------LOG: database system shutdown was interrupted; last known up at 2017-12-04 18:05:23 CSTLOG: database system was not properly shut down; automatic recovery in progressLOG: redo starts at 0/103FE040LOG: redo done at 0/14FFFF68LOG: last completed transaction was at log time 2017-12-04 18:05:09.85515+08PANIC: could not write to file "pg_xlog/xlogtemp.9138": No space left on deviceLOG: startup process (PID 9138) was terminated by signal 6: AbortedLOG: aborting startup due to startup process failure
原因是存放wal日志所在文件系统空间不足。
清理该文件系统下过期的临时文件,或将wal日志存放至更大的系统空间中。
By 徐云鹤
阅读全文
1 0
- postgresql意外中止,无法启动
- MySql无法启动服务报1067:进程意外中止错误
- 无法启动mysql服务 错误1067:进程意外中止
- 无法启动mysql服务 错误1067:进程意外中止
- mysql意外无法启动
- 启动MySQL服务,提示错误1067 进程意外中止
- 在管理工具的服务中启动mysql服务时都会在中途报错。内容为:在 本地计算机 无法启动mysql服务 错误1067:进程意外中止。
- Eclipse意外关闭之后无法启动
- mysql 无法启动 :1067进程意外终止
- MySQL 无法启动:1067进程意外终止
- Mysql意外强制关闭,无法启动解决方案
- MySQl的意外断电后无法启动
- mac的mysql意外无法正常启动
- linux虚拟机意外关闭,无法启动
- Postgresql 安装pgstatspack无法启动
- WebSphere 6.1非正常中止后无法启动的解决办法
- aspnet_wp.exe意外中止的问题
- java UncaughtExceptionHandler 处理线程意外中止
- WebLogic 12 安装过程
- ISCSI
- 小学生开始学Python,还有什么能够阻挡我对Python的向往?
- 17-CSS3 高级技巧 精灵图 滑动门
- Android APK反编译就这么简单 详解(附图)
- postgresql意外中止,无法启动
- 小程序 tab和swiper的结合效果
- 17-CSS3 高级技巧 精灵图 滑动门
- Java中HashMap
- FormValidation程序源码
- 线程与进程概述
- mysql、oracle删除重复数据
- 选择排序
- systemctl 精华篇