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

文章目录

环境

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

相关推荐
Amarantine、沐风倩✨2 小时前
列表接口严禁嵌套 LISTAGG + REGEXP:一次 mission_label 性能事故复盘
java·数据库·sql
好好研究2 小时前
MyBatis - Plus(二)常见注解 + 常见配置
数据库·spring boot·mybatis·mybatis plus
PD我是你的真爱粉2 小时前
MySQL基础-DQL语句与多表查询
数据库·mysql
C#程序员一枚2 小时前
SqlServer如何创建全文索引
数据库·sqlserver
DBA小马哥3 小时前
时序数据库迁移实践指南:面向业务连续性的技术演进路径
数据库·时序数据库·dba
生命因何探索3 小时前
Redis-持久化
数据库·redis·缓存
yjb.gz3 小时前
Shell实现数据库巡检
数据库
福大大架构师每日一题4 小时前
redis 8.4.1 正式发布:安全升级、性能强化与多模块重大修复详解
数据库·redis·安全
魑-魅-魍-魉4 小时前
金仓数据库(KingbaseES)Windows 安装避坑指南:从 Connection Refused 到服务启动的完整实战记录
数据库·金仓