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

文章目录

环境

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

相关推荐
小新同学^O^1 天前
Redis的简单总结
数据库·redis·学习
暴躁小师兄数据学院1 天前
【AI大数据工程师特训笔记】第11讲:正则表达式与正则函数
数据库·mysql
IT龟苓膏1 天前
MySQL InnoDB 内存结构与性能调优:Buffer Pool、脏页、刷盘、临时表和 filesort 一篇讲清
数据库·mysql
城数派1 天前
2026年500米分辨率DEM地形数据(全球/全国/分省/分市)
数据库·arcgis·信息可视化·数据分析·excel
AAA大运重卡何师傅(专跑国道)1 天前
力扣hot100
服务器·前端·数据库
加号31 天前
【MySQL】 审计功能深度解析:从原理到落地实践
数据库·mysql
KaMeidebaby1 天前
卡梅德生物技术快报|Western Blot 实验应用:肺肠轴机制研究全流程技术解析
前端·数据库·人工智能·算法·百度
雨辰AI1 天前
MySQL 迁移至达梦 DM9 完整改造指南|99% SQL 零改动
java·开发语言·数据库·sql·mysql·政务
l1t1 天前
DeepSeek总结的使用实体-组件-系统和基于存在性处理进行Python编程15-17
开发语言·数据库·python
guslegend1 天前
AGENT.md,Skill与工程规范
java·开发语言·数据库