数据库意外中止,无法启动

文章目录

环境

系统平台: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日志!

相关推荐
大师兄666814 分钟前
HarmonyOS7 数据持久化 relationalStore:数据库实战
数据库·arkui·实战案例·harmonyos7
冰茶丿25 分钟前
状态机在嵌入式系统中的应用:不只是switch-case这么简单
数据库·嵌入式硬件·mongodb
AIHR数智引擎27 分钟前
15%对撞40%:WEF白皮书里的AI组织隐忧
数据库·人工智能·经验分享·职场和发展·aihr
卓怡学长33 分钟前
w261springboot基于web学校课程管理系统
java·数据库·spring boot·spring·intellij-idea
嘉泰姆半导体官方36 分钟前
CXAR41337C 双通道数字音频功放 | 2×20W | EQ+DRC | I²S | MCLK-Less - 嘉泰姆电子
前端·javascript·数据库
不坑老师1 小时前
怎么在Word中制作汉字书写笔顺——不坑盒子汉字笔顺步骤在小学低段识字教学中的应用
前端·数据库·人工智能·word·excel·office
苍狼唤1 小时前
SQL+C# 增删改查(练习)
数据库·sql·c#
2301_800256111 小时前
第七章 空间存储与索引 知识点梳理-2
数据库·sql·oracle
草莓熊Lotso2 小时前
【Redis 初阶】 从分布式演进背景到环境搭建全解析
数据库·人工智能·redis·分布式·缓存
倔强的石头_2 小时前
优化器为什么敢把你写的 LEFT JOIN 悄悄改掉?-国产化金仓 KES 优化器设计思路拆解
数据库