文章目录
- 查看进程状态
- 尝试连接
- 查看日志
- [查看 pg\_control 状态](#查看 pg_control 状态)
- 查看服务器重启情况
- [借助 AI ssh mcp server 快速定位](#借助 AI ssh mcp server 快速定位)
-
- 检查日志
- [检查 CPU 占用](#检查 CPU 占用)
- [🔴 诊断结论:PostgreSQL 处于"shutting down"状态,反复进行 end-of-recovery checkpoint 但无法完成](#🔴 诊断结论:PostgreSQL 处于"shutting down"状态,反复进行 end-of-recovery checkpoint 但无法完成)
- 最近的异常日志
- [查看当天的 common-database0 对应的服务日志](#查看当天的 common-database0 对应的服务日志)
- [查看 dmesg](#查看 dmesg)
- [查看 coredump 列表](#查看 coredump 列表)
- [查看 coredump 信息](#查看 coredump 信息)
- 磁盘满是谁导致的
- [AI 总结](#AI 总结)
-
- [问题1:PG 是在 shutdown 完成后的 crash recovery 阶段,还是正在准备完成 shutdown 的阶段?](#问题1:PG 是在 shutdown 完成后的 crash recovery 阶段,还是正在准备完成 shutdown 的阶段?)
-
- [答案:既不是正常的 shutdown 完成,也不是正常 shutdown 过程中。而是进入了"崩溃循环"状态。](#答案:既不是正常的 shutdown 完成,也不是正常 shutdown 过程中。而是进入了"崩溃循环"状态。)
- 问题2:根本原因详细分析
-
- 根因链条(从最底层到最表层)
- 各层证据
- [为什么 checkpointer 会 SIGABRT?](#为什么 checkpointer 会 SIGABRT?)
- 时间线精确还原
- 再次梳理问题定位流程
-
- 一、磁盘满是通过哪个命令抓取到的?
- [二、此环境中 coredump 具体怎么看?是哪里的问题?](#二、此环境中 coredump 具体怎么看?是哪里的问题?)
-
- [2.1 coredump 查看三板斧](#2.1 coredump 查看三板斧)
-
- [① `coredumpctl list` ------ 列出所有 core dump 记录](#①
coredumpctl list—— 列出所有 core dump 记录) - [② `coredumpctl info <PID>` ------ 查看某次 core dump 的详细信息](#②
coredumpctl info <PID>—— 查看某次 core dump 的详细信息) - [③ `coredumpctl` 的 core 文件为什么是 missing/none?](#③
coredumpctl的 core 文件为什么是 missing/none?)
- [① `coredumpctl list` ------ 列出所有 core dump 记录](#①
- [2.2 是哪里的问题?](#2.2 是哪里的问题?)
- 三、完整实战分析流程(全步骤还原)
-
- [第1步:确认 PG 当前状态](#第1步:确认 PG 当前状态)
- [第2步:读 pg\_controldata ------ PG 的"黑匣子"](#第2步:读 pg_controldata —— PG 的"黑匣子")
- [第3步:查系统日志 ------ 找到"第一声枪响"](#第3步:查系统日志 —— 找到"第一声枪响")
- [第4步:查 coredump ------ 确认 PG 怎么崩的](#第4步:查 coredump —— 确认 PG 怎么崩的)
- [第5步:查磁盘 ------ 找根因](#第5步:查磁盘 —— 找根因)
- [第6步:验证 PG 日志 ------ 看 PG 自己说了什么](#第6步:验证 PG 日志 —— 看 PG 自己说了什么)
- [第7步:综合推理 ------ 形成完整因果链](#第7步:综合推理 —— 形成完整因果链)
- 第8步:修复
- 完整分析流程总结图
查看进程状态
shell
[root@ums53 ~]# ps -ef |grep postgres
postgres 2905 1 20 Jun03 ? 03:10:10 /opt/pgsql/bin/postgres -D /opt/pgsql/data/pgdata -p 5432
postgres 4018 2905 0 Jun03 ? 00:09:00 postgres(5432): logger 0
postgres 4029 2905 0 Jun03 ? 00:00:00 postgres(5432): logger 1
postgres 4035 2905 0 Jun03 ? 00:00:00 postgres(5432): logger 2
postgres 3841849 2905 4 10:40 ? 00:00:01 postgres(5432): startup
postgres 3841850 2905 17 10:40 ? 00:00:04 postgres(5432): checkpointer performing end-of-recovery checkpoint
postgres 3841851 2905 0 10:40 ? 00:00:00 postgres(5432): background writer
root 3847454 3846552 0 10:41 pts/2 00:00:00 grep --color=auto postgres
[root@ums53 bak]# systemctl status common-database0
● common-database0.service - PostgreSQL Server
Loaded: loaded (/etc/systemd/system/common-database0.service; enabled; preset: disabled)
Active: active (running) since Wed 2026-06-03 18:55:13 CST; 15h ago
Process: 1122 ExecStart=/opt/pgsql/scripts/pg_ctl.sh start (code=exited, status=0/SUCCESS)
Main PID: 2905 (postgres)
Tasks: 10 (limit: 200809)
Memory: 1.9G
CGroup: /system.slice/common-database0.service
├─ 2905 /opt/pgsql/bin/postgres -D /opt/pgsql/data/pgd>
├─ 4018 "postgres(5432): logger 0 "
├─ 4029 "postgres(5432): logger 1 "
├─ 4035 "postgres(5432): logger 2 "
├─3893584 "postgres(5432): startup "
├─3893585 "postgres(5432): checkpointer performing end-of-recovery checkpoint"
├─3893586 "postgres(5432): background writer "
├─3901440
├─3901441 /opt/pgsql/bin/postgres -D /opt/pgsql/data/pgd>
├─3901442 /opt/pgsql/bin/postgres -D /opt/pgsql/data/pgd>
└─3901443 /opt/pgsql/bin/postgres -D /opt/pgsql/data/pgd>
Jun 03 18:54:14 ums53 systemd[1]: Starting PostgreSQL Server...
Jun 03 18:54:15 ums53 su[1242]: (to postgres) root on none
发现只用几个核心进程, autovacuum launcher 都没有, 业务连接进程也没有
尝试连接
发现无法正常连接
shell
[root@ums53 ~]# update -v
PUB:VMS-B2101.9.5
INN:VMSV200R001B01V9.5
BOARD_TYPE:VMS-U500-H16
BUILD:2026-01-26 00:23
[root@ums53 ~]# export PGPASSWORD=Admin123@ ; /opt/pgsql/bin/pgsql/bin/psql -U postgres -d postgres
psql: error: connection to server on socket "/tmp/.s.PGSQL.5432" failed: FATAL: the database system is not yet accepting connections
DETAIL: Consistent recovery state has not been yet reached.
查看日志
- 遇到 PG问题, 自然想到查看日志
shell
[root@ums53 ~]# cd /var/log/common-database0/
[root@ums53 pg_log]# grep -inEw "(error|fail|failed|fatal)" *.log
[root@ums53 pg_log]#
pg_log 目录下面的日志文件并没有发现明显异常.
- 在看之前压缩的日志
shell
[root@ums53 pg_log]# ll backuplog/
total 2164
-rw-r--r-- 1 root root 320839 Jun 1 19:46 postgresql_error_2026-06-01_19-46-25.log.gz
-rw-r--r-- 1 root root 316554 Jun 2 05:16 postgresql_error_2026-06-02_05-16-25.log.gz
-rw-r--r-- 1 root root 315477 Jun 2 14:56 postgresql_error_2026-06-02_14-56-25.log.gz
-rw-r--r-- 1 root root 323515 Jun 2 23:46 postgresql_error_2026-06-02_23-46-25.log.gz
-rw-r--r-- 1 root root 316270 Jun 3 09:26 postgresql_error_2026-06-03_09-26-25.log.gz
-rw-r--r-- 1 root root 322298 Jun 3 18:06 postgresql_error_2026-06-03_18-06-25.log.gz
-rw-r--r-- 1 root root 285907 Jun 4 02:24 postgresql_error_2026-06-04_02-24-24.log.gz
[root@ums53 pg_log]# vim postgresql_error.log
[root@ums53 pg_log]# ll /bak
total 0
[root@ums53 pg_log]# cp backuplog/* /bak
[root@ums53 pg_log]# cd /bak
[root@ums53 bak]# ls
postgresql_error_2026-06-01_19-46-25.log.gz postgresql_error_2026-06-03_09-26-25.log.gz
postgresql_error_2026-06-02_05-16-25.log.gz postgresql_error_2026-06-03_18-06-25.log.gz
postgresql_error_2026-06-02_14-56-25.log.gz postgresql_error_2026-06-04_02-24-24.log.gz
postgresql_error_2026-06-02_23-46-25.log.gz
[root@ums53 bak]# for file in `ls *gz`; do echo $file; gunzip $file; done
postgresql_error_2026-06-01_19-46-25.log.gz
postgresql_error_2026-06-02_05-16-25.log.gz
postgresql_error_2026-06-02_14-56-25.log.gz
postgresql_error_2026-06-02_23-46-25.log.gz
postgresql_error_2026-06-03_09-26-25.log.gz
postgresql_error_2026-06-03_18-06-25.log.gz
postgresql_error_2026-06-04_02-24-24.log.gz
[root@ums53 bak]# ll
total 29008
-rw-r--r-- 1 root root 4250507 Jun 4 10:46 postgresql_error_2026-06-01_19-46-25.log
-rw-r--r-- 1 root root 4240905 Jun 4 10:46 postgresql_error_2026-06-02_05-16-25.log
-rw-r--r-- 1 root root 4252824 Jun 4 10:46 postgresql_error_2026-06-02_14-56-25.log
-rw-r--r-- 1 root root 4238940 Jun 4 10:46 postgresql_error_2026-06-02_23-46-25.log
-rw-r--r-- 1 root root 4271441 Jun 4 10:46 postgresql_error_2026-06-03_09-26-25.log
-rw-r--r-- 1 root root 4238573 Jun 4 10:46 postgresql_error_2026-06-03_18-06-25.log
-rw-r--r-- 1 root root 4199289 Jun 4 10:46 postgresql_error_2026-06-04_02-24-24.log
[root@ums53 bak]# grep -inEw "(error|fail|failed|fatal)" *.log
postgresql_error_2026-06-01_19-46-25.log:388:2026-06-01 03:15:24.813 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45424) accesscontrol 9692:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:433:2026-06-01 03:15:34.999 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45424) accesscontrol 9692:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:528:2026-06-01 03:16:05.028 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45424) accesscontrol 9692:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:632:2026-06-01 03:17:05.082 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45424) accesscontrol 9692:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:772:2026-06-01 03:19:05.209 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:894:2026-06-01 03:20:11.533 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1001:2026-06-01 03:20:21.633 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1104:2026-06-01 03:20:51.664 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1211:2026-06-01 03:21:51.719 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1239:2026-06-01 03:22:05.235 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1398:2026-06-01 03:23:51.772 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1539:2026-06-01 03:26:05.316 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1642:2026-06-01 03:26:51.853 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(58152) accesscontrol 31292:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1853:2026-06-01 03:30:51.907 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(57758) accesscontrol 37008:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:1888:2026-06-01 03:31:05.420 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(57758) accesscontrol 37008:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:2177:2026-06-01 03:35:52.013 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:2288:2026-06-01 03:37:05.490 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:2558:2026-06-01 03:41:52.082 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:2691:2026-06-01 03:44:05.522 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:2953:2026-06-01 03:48:52.117 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:3161:2026-06-01 03:52:05.608 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:3421:2026-06-01 03:56:52.182 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:3717:2026-06-01 04:01:05.663 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:3978:2026-06-01 04:05:52.252 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:4248:2026-06-01 04:11:05.766 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:4511:2026-06-01 04:15:52.355 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55942) accesscontrol 41119:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:5229:2026-06-01 04:31:05.796 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46064) accesscontrol 74056:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:5485:2026-06-01 04:35:52.473 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46064) accesscontrol 74056:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:6647:2026-06-01 05:01:05.856 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46064) accesscontrol 74056:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:6904:2026-06-01 05:05:52.569 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46064) accesscontrol 74056:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:9441:2026-06-01 06:01:05.969 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(40302) accesscontrol 103715:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:9700:2026-06-01 06:05:52.631 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(40302) accesscontrol 103715:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:12737:2026-06-01 07:12:27.449 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-01_19-46-25.log:12740:2026-06-01 07:12:27.454 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-01_19-46-25.log:14888:2026-06-01 08:01:06.068 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(55440) accesscontrol 182330:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:15164:2026-06-01 08:05:52.670 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(54966) accesscontrol 235629:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-01_19-46-25.log:19077:2026-06-01 09:22:55.590 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-01_19-46-25.log:19080:2026-06-01 09:22:55.594 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-01_19-46-25.log:25492:2026-06-01 11:14:42.249 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-01_19-46-25.log:25495:2026-06-01 11:14:42.249 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_05-16-25.log:601:2026-06-01 11:53:26.612 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_05-16-25.log:604:2026-06-01 11:53:26.613 UTC [unknown] postgres 192.117.2.205(59654) imos 313711:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_14-56-25.log:13738:2026-06-02 02:29:05.276 UTC [unknown] postgres 192.117.2.205(59654) imos 313711:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_14-56-25.log:13741:2026-06-02 02:29:05.277 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:1619:2026-06-02 07:25:53.703 UTC [unknown] postgres 192.117.2.205(59654) imos 313711:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:1622:2026-06-02 07:25:53.704 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:2760:2026-06-02 07:45:12.983 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:2763:2026-06-02 07:45:12.984 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:2766:2026-06-02 07:45:13.167 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:2769:2026-06-02 07:45:13.168 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:3301:2026-06-02 07:50:22.538 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:3304:2026-06-02 07:50:22.539 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:5027:2026-06-02 08:30:20.497 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:5030:2026-06-02 08:30:20.498 UTC [unknown] postgres 192.117.2.205(59654) imos 313711:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:8034:2026-06-02 09:33:43.552 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(56038) accesscontrol 1185297:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:8071:2026-06-02 09:33:53.656 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(56038) accesscontrol 1185297:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:8169:2026-06-02 09:34:23.683 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(56038) accesscontrol 1185297:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:8269:2026-06-02 09:35:23.741 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(56038) accesscontrol 1185297:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:8416:2026-06-02 09:37:23.857 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(56038) accesscontrol 1185297:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:8589:2026-06-02 09:40:23.923 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39428) accesscontrol 1234111:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:8813:2026-06-02 09:44:23.943 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39428) accesscontrol 1234111:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:9076:2026-06-02 09:49:24.024 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39428) accesscontrol 1234111:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:9393:2026-06-02 09:55:24.066 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39428) accesscontrol 1234111:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:9755:2026-06-02 10:02:24.166 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45180) accesscontrol 1252603:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:10142:2026-06-02 10:10:24.237 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45180) accesscontrol 1252603:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:10585:2026-06-02 10:19:24.344 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45180) accesscontrol 1252603:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:11061:2026-06-02 10:29:24.421 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45180) accesscontrol 1252603:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:11971:2026-06-02 10:49:24.493 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45180) accesscontrol 1252603:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:12898:2026-06-02 11:08:56.431 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:12901:2026-06-02 11:08:56.434 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:13350:2026-06-02 11:19:24.535 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(45180) accesscontrol 1252603:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:15608:2026-06-02 12:08:12.045 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:15635:2026-06-02 12:08:22.161 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:15742:2026-06-02 12:08:52.187 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:15835:2026-06-02 12:09:52.242 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16009:2026-06-02 12:11:52.359 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16135:2026-06-02 12:13:48.083 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16175:2026-06-02 12:13:58.174 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16270:2026-06-02 12:14:28.202 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16343:2026-06-02 12:14:52.423 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16431:2026-06-02 12:15:28.270 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16885:2026-06-02 12:17:28.315 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:16998:2026-06-02 12:18:52.496 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:17068:2026-06-02 12:19:24.628 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:17167:2026-06-02 12:20:28.401 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:17367:2026-06-02 12:23:52.611 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:17440:2026-06-02 12:24:28.455 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:17719:2026-06-02 12:29:28.549 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:17785:2026-06-02 12:29:52.663 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:18081:2026-06-02 12:35:28.586 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:18194:2026-06-02 12:36:52.762 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:18483:2026-06-02 12:42:28.694 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:18628:2026-06-02 12:44:52.833 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:18880:2026-06-02 12:49:24.224 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:18883:2026-06-02 12:49:24.226 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:18887:2026-06-02 12:49:24.813 UTC [unknown] postgres 192.117.2.205(59654) imos 313711:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:18890:2026-06-02 12:49:24.813 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-02_23-46-25.log:19042:2026-06-02 12:50:28.771 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:19237:2026-06-02 12:53:52.863 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:19529:2026-06-02 12:59:28.829 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:19771:2026-06-02 13:03:52.898 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:20064:2026-06-02 13:09:28.937 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(44322) accesscontrol 1344734:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:20825:2026-06-02 13:23:52.917 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46106) accesscontrol 1414609:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:21123:2026-06-02 13:29:29.050 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46106) accesscontrol 1414609:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:22201:2026-06-02 13:53:53.006 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46106) accesscontrol 1414609:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:22495:2026-06-02 13:59:29.142 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46106) accesscontrol 1414609:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:23395:2026-06-02 14:19:24.672 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46106) accesscontrol 1414609:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:24912:2026-06-02 14:53:53.042 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(51602) accesscontrol 1448996:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-02_23-46-25.log:25200:2026-06-02 14:59:29.163 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(51602) accesscontrol 1448996:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_09-26-25.log:3171:2026-06-02 16:53:53.111 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42612) accesscontrol 1510309:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_09-26-25.log:3469:2026-06-02 16:59:29.232 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(41154) accesscontrol 1536179:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:6988:2026-06-03 03:50:25.198 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:7030:2026-06-03 03:50:35.268 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:7129:2026-06-03 03:51:05.303 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:7234:2026-06-03 03:52:05.352 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:7369:2026-06-03 03:54:05.469 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:7546:2026-06-03 03:57:05.552 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:7764:2026-06-03 04:01:05.595 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:8048:2026-06-03 04:06:05.683 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(48824) accesscontrol 1886712:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:8367:2026-06-03 04:12:05.720 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(34740) accesscontrol 1933810:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:8724:2026-06-03 04:19:05.775 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(34740) accesscontrol 1933810:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:9134:2026-06-03 04:27:05.862 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(34740) accesscontrol 1933810:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:9573:2026-06-03 04:36:05.897 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(34740) accesscontrol 1933810:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:10063:2026-06-03 04:46:05.998 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(34740) accesscontrol 1933810:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:10999:2026-06-03 05:06:06.026 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(34740) accesscontrol 1933810:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:12366:2026-06-03 05:36:06.090 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(36840) accesscontrol 1984425:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:15045:2026-06-03 06:36:06.181 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(40556) accesscontrol 2032155:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:20282:2026-06-03 08:36:06.239 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(46866) accesscontrol 2107272:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:20913:2026-06-03 08:49:16.566 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:20945:2026-06-03 08:49:26.597 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:21048:2026-06-03 08:49:56.631 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:21140:2026-06-03 08:50:56.692 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:21295:2026-06-03 08:52:56.809 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:21468:2026-06-03 08:55:56.891 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:21695:2026-06-03 08:59:56.946 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:21965:2026-06-03 09:04:57.061 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(35398) accesscontrol 2137853:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:22277:2026-06-03 09:10:57.113 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39744) accesscontrol 2156308:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:22643:2026-06-03 09:17:57.230 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39744) accesscontrol 2156308:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:23033:2026-06-03 09:25:57.302 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(39744) accesscontrol 2156308:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:23419:2026-06-03 09:32:30.028 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:23422:2026-06-03 09:32:30.029 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:23842:2026-06-03 09:34:57.353 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:24011:2026-06-03 09:37:32.137 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:24014:2026-06-03 09:37:32.138 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:24468:2026-06-03 09:41:16.925 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:24471:2026-06-03 09:41:16.926 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:24633:2026-06-03 09:44:57.396 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-03_18-06-25.log:24966:2026-06-03 09:51:26.165 UTC [unknown] postgres 192.117.2.205(50188) imos 1884980:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:24969:2026-06-03 09:51:26.166 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:25755:2026-06-03 09:56:31.215 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:25758:2026-06-03 09:56:31.216 UTC [unknown] postgres 192.117.2.205(34302) imos 29795:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-03_18-06-25.log:26380:2026-06-03 10:04:57.499 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-04_02-24-24.log:81:2026-06-03 10:08:15.116 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-04_02-24-24.log:84:2026-06-03 10:08:15.118 UTC [unknown] postgres 192.117.2.205(34298) imos 29794:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-04_02-24-24.log:963:2026-06-03 10:28:38.746 UTC [unknown] postgres 192.117.2.205(36382) imos 8721:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-04_02-24-24.log:966:2026-06-03 10:28:38.747 UTC [unknown] postgres 192.117.2.205(59890) imos 313749:ERROR: duplicate key value violates unique constraint "pk_tbl_dc_info"
postgresql_error_2026-06-04_02-24-24.log:1254:2026-06-03 10:34:57.609 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-04_02-24-24.log:1624:2026-06-03 10:42:02.451 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-04_02-24-24.log:1664:2026-06-03 10:42:12.555 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-04_02-24-24.log:1758:2026-06-03 10:42:42.584 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
postgresql_error_2026-06-04_02-24-24.log:1850:2026-06-03 10:43:42.649 UTC PostgreSQL JDBC Driver postgres 192.117.2.205(42022) accesscontrol 2181665:ERROR: syntax error at or near "and" at character 418
也没有查看到明显的与此次异常相关的信息.大都是语法错误.
查看 pg_control 状态
shell
[root@ums53 bak]# /opt/pgsql/bin/pgsql/bin/pg_controldata /opt/pgsql/data/pgdata/
pg_control version number: 1300
Catalog version number: 202209061
Database system identifier: 7646250698750929143
Database cluster state: shutting down
pg_control last modified: Thu 04 Jun 2026 10:47:42 AM CST
Latest checkpoint location: 0/1DC011A8
Latest checkpoint's REDO location: 0/1DC00340
Latest checkpoint's REDO WAL file: 00000001000000000000001D
Latest checkpoint's TimeLineID: 1
Latest checkpoint's PrevTimeLineID: 1
Latest checkpoint's full_page_writes: on
Latest checkpoint's NextXID: 0:76603
Latest checkpoint's NextOID: 57198
Latest checkpoint's NextMultiXactId: 1
Latest checkpoint's NextMultiOffset: 0
Latest checkpoint's oldestXID: 719
Latest checkpoint's oldestXID's DB: 1
Latest checkpoint's oldestActiveXID: 76603
Latest checkpoint's oldestMultiXid: 1
Latest checkpoint's oldestMulti's DB: 1
Latest checkpoint's oldestCommitTsXid:0
Latest checkpoint's newestCommitTsXid:0
Time of latest checkpoint: Thu 04 Jun 2026 02:40:22 AM CST
Fake LSN counter for unlogged rels: 0/3E8
Minimum recovery ending location: 0/0
Min recovery ending loc's timeline: 0
Backup start location: 0/0
Backup end location: 0/0
End-of-backup record required: no
wal_level setting: replica
wal_log_hints setting: on
max_connections setting: 1200
max_worker_processes setting: 16
max_wal_senders setting: 10
max_prepared_xacts setting: 0
max_locks_per_xact setting: 64
track_commit_timestamp setting: off
Maximum data alignment: 8
Database block size: 8192
Blocks per segment of large relation: 16777216
WAL block size: 8192
Bytes per WAL segment: 16777216
Maximum length of identifiers: 64
Maximum columns in an index: 32
Maximum size of a TOAST chunk: 1996
Size of a large-object chunk: 2048
Date/time type storage: 64-bit integers
Float8 argument passing: by value
Data page checksum version: 0
Mock authentication nonce: bc041df1ca591375a96260a9f5315ff76516f31aed5c0dd1a218dd487c9d91a8
[root@ums53 bak]#
查看服务器重启情况
shell
[root@ums53 bak]# last reboot |head
reboot system boot 6.4.0 Wed Jun 3 18:54 still running
reboot system boot 6.4.0 Mon Jun 1 10:46 still running
reboot system boot 6.4.0 Wed May 20 19:54 - 10:45 (11+14:51)
reboot system boot 6.4.0 Mon May 18 14:42 - 10:45 (13+20:03)
reboot system boot 6.4.0 Thu May 7 21:23 - 14:42 (10+17:18)
reboot system boot 6.4.0 Thu May 7 16:20 - 21:22 (05:01)
reboot system boot 6.4.0 Fri May 1 15:32 - 16:20 (6+00:48)
reboot system boot 6.4.0 Tue Apr 28 17:59 - 16:20 (8+22:21)
reboot system boot 6.4.0 Mon Apr 27 15:20 - 17:58 (1+02:38)
reboot system boot 6.4.0 Mon Apr 27 15:09 - 15:19 (00:10)
发现 2026-06-03 18:54 reobot 过
借助 AI ssh mcp server 快速定位
检查日志
shell
[root@ums53 common-database0]# cat /var/log/common-database0/pg_log/postgresql_error.log | grep -inE '(FATAL|PANIC|recovery|shutting|startup|yet|consistent)'
[root@ums53 common-database0]#
zcat /var/log/common-database0/pg_log/backuplog/postgresql_error_2026-06-04_02-24-24.log.gz | grep -aiE '(FATAL|PANIC|recovery|shutting|startup|yet|consistent)'
检查 CPU 占用
shell
top -bn1 | head -5 && echo '---' && ps aux --sort=-%cpu | head -10
Result:
top - 10:51:34 up 15:57, 4 users, load average: 22.86, 22.22, 21.71
Tasks: 363 total, 2 running, 360 sleeping, 0 stopped, 1 zombie
%Cpu(s): 7.3 us, 41.8 sy, 0.0 ni, 45.5 id, 1.8 wa, 1.8 hi, 1.8 si, 0.0 st
MiB Mem : 31420.0 total, 344.4 free, 11753.3 used, 21917.2 buff/cache
MiB Swap: 0.0 total, 0.0 free, 0.0 used. 19666.7 avail Mem
---
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 3945282 600 0.0 26664 5120 pts/3 R+ 10:51 0:00 ps aux --sort=-%cpu
postgres 2905 20.3 0.4 2364404 135072 ? Ss Jun03 194:48 /opt/pgsql/bin/postgres -D /opt/pgsql/data/pgdata -p 5432
root 1164 17.6 1.4 4087108 463884 ? Ssl Jun03 169:10 /opt/jdk1.8/jdk1.8_x86/bin/java -jar -Xms10m -Xmx512m -Xss256k /opt/func-AS0/bin/daiswebserver.jar --spring.config.location=/opt/func-AS0/config/
root 3935906 16.1 0.0 15760 7040 ? DNs 10:50 0:11 /usr/lib/systemd/systemd-coredump
root 2449 16.0 0.1 733520 36256 ? Sl Jun03 153:20 ./bin/swGoServer
root 3779099 13.5 0.0 0 0 ? I 10:33 2:25 [kworker/u8:1-ext4-rsv-conversion]
postgres 3935054 12.6 6.9 2364516 2225520 ? Ss 10:50 0:09 postgres(5432): checkpointer performing end-of-recovery checkpoint
root 3411209 8.3 0.0 0 0 ? R 09:52 4:53 [kworker/u8:0+flush-8:64]
root 3722 6.7 2.1 6438308 689076 ? Sl Jun03 64:58 /opt/jdk1.8/jdk1.8_x86/bin/java -server -Xms128m -Xmx128m -Xss512k -XX:+UseG1GC -XX:G1HeapRegionSize=16m -XX:G1ReservePercent=25 -XX:InitiatingHeapOccupancyPercent=30 -XX:SoftRefLRUPolicyMSPerMB=0 -verbose:gc -Xloggc:/dev/shm/rmq_srv_gc_%p_%t.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintAdaptiveSizePolicy -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=30m -XX:-OmitStackTraceInFastThrow -XX:+AlwaysPreTouch -XX:MaxDirectMemorySize=15g -XX:-UseLargePages -XX:-UseBiasedLocking -cp .:/opt/common-rocketMQBroker0/bin/../conf:/opt/common-rocketMQBroker0/bin/../lib/*: -Drmq.logback.configurationFile=/opt/common-rocketMQBroker0/conf/rmq.broker.logback.xml org.apache.rocketmq.broker.BrokerStartup -c /opt/common-rocketMQBroker0/bin/../conf/broker.conf
🔴 诊断结论:PostgreSQL 处于"shutting down"状态,反复进行 end-of-recovery checkpoint 但无法完成
核心证据
| 证据 | 来源 | 含义 |
|---|---|---|
pg_controldata 显示 Database cluster state: shutting down |
你提供的 + 我实时验证 | 数据库控制文件记录的状态是"正在关闭" ,而不是 shut down(正常关闭) |
pg_control last modified: Thu 04 Jun 2026 10:47:42 AM CST |
实时验证 | 控制文件在约 4 分钟前还被修改,说明 checkpoint 进程仍在运行/挣扎 |
postgres(5432): startup 进程持续存在 |
ps aux |
启动进程一直在做 recovery,始终未完成 |
postgres(5432): checkpointer performing end-of-recovery checkpoint |
ps aux |
checkpointer 在做"end-of-recovery"检查点,但迟迟完不成 |
psql: FATAL: the database system is not yet accepting connections / Consistent recovery state has not been yet reached |
实时验证 | 数据库因为 recovery 未完成,拒绝所有连接 |
| 主进程 PID 2905 CPU 占用 20.3%,checkpoint 进程占 1.1% 内存(376MB) | ps aux |
checkpoint 在工作但很慢 |
系统负载 22+,%sy 高达 41.8%,kworker 内核线程活跃 |
top |
系统 I/O 压力极大,checkpoint 受 I/O 制约 |
没有 standby.signal / recovery.signal,APP_HA_IDENTIFY=0 |
实时验证 | 这是单机模式,不是 standby 恢复场景 |
最近的异常日志
shell
2026-06-03 18:41:59.198 UTC [unknown] postgres 192.117.2.205(43954) park 253919:LOG: connection authenticated: identity="postgres" method=md5 (/opt/pgsql/data/pgdata/pg_hba.conf:11)
2026-06-03 18:41:59.198 UTC [unknown] postgres 192.117.2.205(43954) park 253919:LOG: connection authorized: user=postgres database=park
2026-06-03 18:41:59.202 UTC [unknown] postgres 192.117.2.205(43954) park 253919:LOG: disconnection: session time: 0:00:00.011 user=postgres database=park host=192.117.2.205 port=43954
2026-06-03 18:42:19.143 UTC [unknown] [unknown] 192.117.2.205(40062) [unknown] 254089:LOG: connection received: host=192.117.2.205 port=40062
2026-06-03 18:42:19.150 UTC [unknown] postgres 192.117.2.205(40062) park 254089:LOG: connection authenticated: identity="postgres" method=md5 (/opt/pgsql/data/pgdata/pg_hba.conf:11)2026-06-04 04:26:59.568 UTC [unknown] [unknown] 192.117.2.205(58508) [unknown] 618465:LOG: connection received: host=192.117.2.205 port=58508
2026-06-04 04:26:59.568 UTC [unknown] [unknown] 192.117.2.205(58508) [unknown] 618465:LOG: PID 0 in cancel request did not match any process
2026-06-04 04:26:59.570 UTC [unknown] postgres 192.117.2.205(58492) uap 618464:FATAL: the database system is not yet accepting connections
2026-06-04 04:26:59.570 UTC [unknown] postgres 192.117.2.205(58492) uap 618464:DETAIL: Consistent recovery state has not been yet reached.
2026-06-04 04:26:59.570 UTC [unknown] postgres 192.117.2.205(58492) uap 618464:BACKTRACE:
Process Info:
pid: 618464
type: client backend
sql: <NULL>
Backtrace:
#0 errfinish+0x2ec [0x974c2c]
#1 ProcessStartupPacket.cold+0x4a6 [0x4e8173]
#2 ServerLoop+0xd30 [0x7c6800]
#3 PostmasterMain+0xcc0 [0x7c7840]
#4 main+0x1bb [0x51892b]
#5 __libc_init_first+0x90 [0x7fdfa2823f10]
#6 __libc_start_main+0x89 [0x7fdfa2823fc9]
#7 _start+0x29 [0x518f36]
可以看到 在 2026-06-03 18:42:19.150 也就是 06-04 02:42 分钟 此处 PG 服务还是正常接受连接的
紧接着下面的日志为 2026-06-04 04:26:59.568 UTC 也就是 06-04 10:26 才打日志, 并且是进入 crash recovery 状态.
说明在此期间出现了问题
查看当天的 common-database0 对应的服务日志
shell
[root@ums53 bak]# journalctl --since '2026-06-04 00:01' --until '2026-06-04 23:59' | grep -iE '(postgres|common-database|oom|kill|signal|shutdown|memory|coredump)' |head
Jun 04 00:05:01 ums53 CROND[172451]: (root) CMD (flock -xn /tmp/autoclean_ums_sub_table.lock -c /opt/pgsql/scripts/autoclean_ums_sub_table.sh >/dev/null 2>&1)
Jun 04 00:05:05 ums53 CROND[172449]: (root) CMDEND (flock -xn /tmp/autoclean_ums_sub_table.lock -c /opt/pgsql/scripts/autoclean_ums_sub_table.sh >/dev/null 2>&1)
Jun 04 02:45:22 ums53 systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 04 02:45:50 ums53 systemd-coredump[255663]: elfutils disabled, parsing ELF objects not supported
Jun 04 02:45:50 ums53 systemd-coredump[255663]: Process 4076 (postgres) of user 1001 dumped core.
Jun 04 02:45:51 ums53 systemd[1]: systemd-coredump@0-255662-0.service: Deactivated successfully.
Jun 04 02:46:18 ums53 systemd-coredump[256428]: Removed old coredump core.postgres.1001.a90835c07150428abd9262f01ffdfff4.4076.1780512322000000.lz4.
Jun 04 02:46:18 ums53 systemd-coredump[256428]: elfutils disabled, parsing ELF objects not supported
Jun 04 02:46:18 ums53 systemd-coredump[256428]: Process 255935 (postgres) of user 1001 dumped core.
Jun 04 02:46:20 ums53 systemd[1]: systemd-coredump@1-256423-0.service: Deactivated successfully.
[root@ums53 bak]#
[root@ums53 bak]#
[root@ums53 bak]# journalctl --since '2026-06-04 00:01' --until '2026-06-04 23:59' | grep -iE '(postgres|common-database|oom|kill|signal|shutdown|memory|coredump)' |tail
Jun 04 12:24:08 ums53 systemd[1]: systemd-coredump@774-585449-0.service: Deactivated successfully.
Jun 04 12:25:08 ums53 systemd-coredump[593446]: Cannot store coredump of 592617 (postgres): No space left on device
Jun 04 12:25:09 ums53 systemd-coredump[593446]: Process 592617 (postgres) of user 1001 dumped core.
Jun 04 12:25:09 ums53 systemd[1]: systemd-coredump@775-593440-0.service: Deactivated successfully.
Jun 04 12:26:04 ums53 systemd-coredump[602286]: Cannot store coredump of 602012 (postgres): No space left on device
Jun 04 12:26:05 ums53 systemd-coredump[602286]: Process 602012 (postgres) of user 1001 dumped core.
Jun 04 12:26:05 ums53 systemd[1]: systemd-coredump@776-602281-0.service: Deactivated successfully.
Jun 04 12:27:05 ums53 systemd-coredump[612410]: elfutils disabled, parsing ELF objects not supported
Jun 04 12:27:05 ums53 systemd-coredump[612410]: Process 611851 (postgres) of user 1001 dumped core.
Jun 04 12:27:06 ums53 systemd[1]: systemd-coredump@777-612402-0.service: Deactivated successfully.
[root@ums53 bak]#
[root@ums53 bak]# journalctl --since '2026-06-04 00:01' --until '2026-06-04 23:59' | grep -iE '(postgres|common-database|oom|kill|signal|shutdown|memory|coredump)' |grep space -iw |head
Jun 04 10:47:34 ums53 systemd-coredump[3893892]: Failed to compress (unnamed temporary file): No space left on device
Jun 04 10:48:57 ums53 systemd-coredump[3907007]: Failed to compress (unnamed temporary file): No space left on device
Jun 04 10:50:16 ums53 systemd-coredump[3921871]: Failed to compress (unnamed temporary file): No space left on device
Jun 04 10:53:04 ums53 systemd-coredump[3947242]: Cannot store coredump of 3946135 (postgres): No space left on device
Jun 04 10:54:14 ums53 systemd-coredump[3961624]: Cannot store coredump of 3960545 (postgres): No space left on device
Jun 04 10:55:33 ums53 systemd-coredump[3972283]: Failed to compress (unnamed temporary file): No space left on device
Jun 04 10:58:22 ums53 systemd-coredump[3998904]: Failed to compress (unnamed temporary file): No space left on device
Jun 04 10:59:32 ums53 systemd-coredump[4013654]: Cannot store coredump of 4012711 (postgres): No space left on device
Jun 04 11:00:37 ums53 systemd-coredump[4026335]: Cannot store coredump of 4025970 (postgres): No space left on device
Jun 04 11:02:00 ums53 systemd-coredump[4036484]: Cannot store coredump of 4035342 (postgres): No space left on device
[root@ums53 bak]#
查看 dmesg
shell
[root@ums53 bak]# dmesg -T 2>/dev/null | grep -iE '(oom|kill|out of memory|postgres|common-database)'
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-stor0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-stor0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-parkingManage0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-parkingManage0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-live0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-live0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-imageStorage0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-imageStorage0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-diskConfigurator0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-diskConfigurator0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-dataFeed0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-dataFeed0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-dataCenter0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-dataCenter0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-XWall0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-XWall0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-VMDataProxy0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-VMDataProxy0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-UMSBase0.service:5: Failed to add dependency on postgresql, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-UMSBase0.service:6: Failed to add dependency on postgresql, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-UAP0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-UAP0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-RAS0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-RAS0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-PTZ0.service:5: Failed to add dependency on common-database, ignoring: Invalid argument
[Wed Jun 3 18:54:12 2026] systemd[1]: /etc/systemd/system/func-PTZ0.service:6: Failed to add dependency on common-database, ignoring: Invalid argument
[root@ums53 bak]#
[root@ums53 bak]#
查看 coredump 列表
shell
[root@ums53 bak]# coredumpctl list |grep postgres
Thu 2026-06-04 02:45:50 CST 4076 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:46:18 CST 255935 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:46:46 CST 258501 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:47:12 CST 261109 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:47:38 CST 263622 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:48:04 CST 266121 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:48:29 CST 268698 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:48:54 CST 271139 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:49:18 CST 273647 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:49:43 CST 275931 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:50:09 CST 278339 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:50:35 CST 280865 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:50:59 CST 283340 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:51:23 CST 285913 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:51:48 CST 288259 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:52:14 CST 290766 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:52:38 CST 293285 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:53:03 CST 295891 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:53:27 CST 298378 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:53:53 CST 300848 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:54:17 CST 303495 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:54:43 CST 305953 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:55:10 CST 308527 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:55:35 CST 311038 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:55:58 CST 313658 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:56:22 CST 315990 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:56:46 CST 318317 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:57:11 CST 320728 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:57:36 CST 323217 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:57:59 CST 325729 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:58:24 CST 328113 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:58:48 CST 330850 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:59:11 CST 333291 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 02:59:36 CST 335723 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:00:03 CST 338194 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:00:28 CST 341092 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:00:53 CST 343677 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:01:17 CST 346157 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:01:42 CST 348748 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:02:07 CST 351513 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:02:32 CST 354149 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:02:57 CST 356709 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:03:24 CST 359476 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:03:51 CST 362111 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:04:18 CST 364779 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:04:45 CST 367571 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:05:10 CST 370291 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:05:34 CST 372814 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:05:59 CST 375226 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:06:22 CST 378091 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:06:46 CST 380436 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:07:10 CST 382951 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:07:36 CST 385363 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:08:04 CST 388411 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:08:28 CST 391142 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:08:56 CST 393722 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:09:21 CST 396747 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:09:47 CST 399328 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:10:12 CST 401892 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:10:38 CST 404533 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:11:02 CST 407548 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:11:27 CST 410199 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:11:53 CST 412818 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:12:17 CST 415832 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:12:42 CST 418461 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:13:06 CST 421041 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:13:32 CST 423622 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:13:59 CST 426659 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:14:24 CST 429249 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:14:48 CST 431865 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:15:14 CST 434599 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:15:38 CST 437359 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:16:01 CST 439876 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:16:27 CST 442327 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:16:52 CST 445378 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:17:18 CST 447898 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:17:43 CST 450509 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:18:08 CST 453112 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:18:33 CST 456153 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:18:59 CST 458753 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:19:24 CST 461422 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:19:49 CST 464477 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:20:13 CST 467141 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:20:38 CST 469718 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:21:06 CST 472233 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:21:30 CST 475472 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:21:53 CST 478086 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:22:19 CST 480533 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:22:46 CST 483418 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:23:12 CST 486309 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:23:37 CST 488908 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:24:03 CST 491563 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:24:27 CST 494747 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:24:53 CST 497306 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:25:18 CST 499966 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:25:43 CST 502585 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:26:06 CST 505510 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:26:29 CST 508006 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:26:56 CST 510417 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:27:20 CST 513717 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:27:44 CST 516323 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:28:09 CST 518811 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:28:35 CST 521486 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:29:00 CST 524590 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:29:24 CST 527380 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:29:50 CST 529892 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:30:16 CST 532716 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:30:39 CST 535616 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:31:02 CST 538098 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:31:30 CST 540428 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:31:54 CST 543845 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:32:18 CST 546454 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:32:46 CST 549100 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:33:13 CST 551909 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:33:38 CST 555056 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:34:02 CST 557674 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:34:29 CST 560306 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:34:53 CST 563738 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:35:17 CST 566193 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:35:41 CST 568734 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:36:07 CST 571295 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:36:33 CST 574732 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:36:59 CST 577380 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:37:25 CST 579936 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:37:50 CST 583391 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:38:14 CST 585979 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:38:39 CST 588624 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:39:06 CST 591312 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:39:30 CST 594828 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:39:53 CST 597327 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:40:18 CST 599797 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:40:44 CST 602564 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:41:07 CST 605743 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:41:32 CST 608204 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:41:59 CST 610808 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:42:24 CST 614284 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:42:49 CST 617065 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:43:14 CST 619610 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:43:43 CST 622218 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:44:09 CST 625805 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:44:34 CST 628401 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:45:02 CST 630952 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:45:27 CST 634567 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:45:52 CST 637142 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:46:17 CST 639729 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:46:45 CST 642487 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:47:09 CST 645904 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:47:33 CST 648560 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:48:00 CST 651020 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:48:26 CST 654570 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:48:51 CST 657144 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:49:16 CST 659717 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:49:44 CST 662450 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:50:09 CST 665852 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:50:33 CST 668482 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:51:00 CST 670954 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:51:29 CST 674518 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:51:53 CST 677136 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:52:17 CST 679607 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:52:44 CST 682224 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:53:08 CST 685593 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:53:31 CST 688096 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:54:00 CST 690499 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:54:24 CST 694254 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:54:48 CST 696835 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:55:14 CST 699301 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:55:41 CST 701880 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:56:05 CST 705544 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:56:30 CST 708113 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:57:02 CST 710630 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:57:29 CST 714635 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:57:56 CST 717270 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:58:20 CST 719917 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:58:48 CST 722561 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:59:13 CST 726015 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 03:59:40 CST 728510 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:00:08 CST 730984 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:00:31 CST 734874 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:00:57 CST 737462 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:01:23 CST 740168 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:01:48 CST 743380 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:02:15 CST 746334 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:02:38 CST 749016 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:03:06 CST 751366 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:03:30 CST 755214 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:03:53 CST 757742 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:04:19 CST 760148 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:04:47 CST 763040 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:05:12 CST 766426 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:05:36 CST 769077 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:06:05 CST 771602 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:06:29 CST 775643 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:06:53 CST 778069 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:07:18 CST 780585 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:07:45 CST 783332 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:08:10 CST 786756 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:08:36 CST 789472 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:09:05 CST 792076 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:09:29 CST 795982 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:09:53 CST 798485 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:10:19 CST 800865 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:10:46 CST 804033 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:11:09 CST 807491 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:11:34 CST 810006 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:12:02 CST 812654 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:12:27 CST 816628 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:12:52 CST 819203 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:13:16 CST 821804 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:13:43 CST 824333 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:14:09 CST 828180 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:14:33 CST 830867 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:15:01 CST 833220 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:15:26 CST 837237 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:15:52 CST 839817 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:16:19 CST 842462 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:16:45 CST 845236 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:17:11 CST 848781 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:17:34 CST 851473 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:18:03 CST 853834 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:18:29 CST 858022 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:18:54 CST 860642 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:19:18 CST 863246 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:19:48 CST 865988 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:20:14 CST 869877 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:20:39 CST 872563 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:21:08 CST 875259 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:21:33 CST 879490 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:21:56 CST 882067 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:22:21 CST 884630 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:22:48 CST 887749 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:23:13 CST 891242 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:23:41 CST 893865 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:24:09 CST 896649 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:24:33 CST 900790 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:24:56 CST 903347 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:25:20 CST 905802 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:25:49 CST 908305 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:26:13 CST 912298 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:26:40 CST 914877 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:27:08 CST 917442 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:27:32 CST 921627 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:27:55 CST 924081 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:28:20 CST 926557 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:28:48 CST 929397 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:29:11 CST 933248 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:29:36 CST 935649 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:30:07 CST 938273 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:30:33 CST 942679 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:31:01 CST 945313 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:31:27 CST 947976 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:31:53 CST 951452 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:32:15 CST 954527 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:32:39 CST 956896 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:33:09 CST 959370 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:33:34 CST 963624 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:33:58 CST 966191 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:34:27 CST 968819 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:34:53 CST 972345 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:35:17 CST 975631 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:35:41 CST 978217 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:36:10 CST 980727 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:36:36 CST 985052 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:37:01 CST 987586 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:37:30 CST 990241 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:37:55 CST 994607 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:38:21 CST 997257 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:38:43 CST 999809 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:39:12 CST 1002228 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:39:38 CST 1006589 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:40:04 CST 1009162 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:40:36 CST 1011823 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:41:00 CST 1016179 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:41:28 CST 1018751 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:41:56 CST 1021607 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:42:22 CST 1025225 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:42:48 CST 1028523 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:43:14 CST 1031138 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:43:43 CST 1033652 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:44:09 CST 1038096 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:44:34 CST 1040721 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:45:04 CST 1043356 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:45:29 CST 1047947 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:45:52 CST 1050564 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:46:18 CST 1053069 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:46:50 CST 1056033 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:47:14 CST 1060276 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:47:39 CST 1062655 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:48:10 CST 1065323 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:48:35 CST 1070021 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:49:00 CST 1072770 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:49:30 CST 1075482 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:49:56 CST 1079755 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:50:20 CST 1082635 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:50:45 CST 1085276 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:51:17 CST 1087939 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:51:41 CST 1092474 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:52:04 CST 1095035 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:52:34 CST 1097566 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:53:00 CST 1102091 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:53:24 CST 1104794 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:53:49 CST 1107228 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:54:18 CST 1110195 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:54:44 CST 1114291 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:55:08 CST 1116890 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:55:38 CST 1119514 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:56:03 CST 1124226 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:56:27 CST 1126809 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:56:53 CST 1129261 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:57:21 CST 1132271 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:57:44 CST 1136245 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:58:09 CST 1138692 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:58:41 CST 1141285 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:59:04 CST 1146136 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 04:59:32 CST 1148672 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:00:02 CST 1151411 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:00:26 CST 1155960 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:00:49 CST 1158686 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:01:14 CST 1161065 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:01:47 CST 1163618 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:02:12 CST 1168474 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:02:36 CST 1171063 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:03:09 CST 1173643 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:03:34 CST 1178527 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:03:57 CST 1181096 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:04:25 CST 1183512 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:04:53 CST 1187026 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:05:16 CST 1190892 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:05:42 CST 1193299 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:06:13 CST 1195942 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:06:38 CST 1200924 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:07:02 CST 1203588 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:07:31 CST 1206090 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:08:00 CST 1210202 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:08:26 CST 1213286 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:08:52 CST 1215946 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:09:23 CST 1219232 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:09:49 CST 1223403 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:10:12 CST 1225840 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:10:44 CST 1228216 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:11:09 CST 1233234 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:11:33 CST 1235834 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:12:03 CST 1238365 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:12:29 CST 1242753 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:12:55 CST 1245898 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:13:18 CST 1248588 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:13:51 CST 1251239 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:14:14 CST 1255989 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:14:41 CST 1258404 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:15:12 CST 1261022 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:15:39 CST 1266053 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:16:05 CST 1268601 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:16:36 CST 1271283 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:16:59 CST 1276290 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:17:26 CST 1278710 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:17:52 CST 1281409 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:18:21 CST 1284382 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:18:45 CST 1288819 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:19:09 CST 1291226 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:19:42 CST 1293661 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:21:17 CST 1303423 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:21:43 CST 1308427 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:22:09 CST 1311226 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:22:42 CST 1313890 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:23:08 CST 1319014 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:23:32 CST 1321706 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:24:37 CST 1324157 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:25:04 CST 1328945 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:25:32 CST 1332236 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:26:38 CST 1336613 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:27:11 CST 1343300 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:27:35 CST 1348457 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:28:05 CST 1350973 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:28:38 CST 1353665 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:29:47 CST 1358548 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:30:18 CST 1365232 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:30:44 CST 1370223 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:31:08 CST 1372894 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:31:41 CST 1375359 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:32:06 CST 1380594 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:32:30 CST 1383042 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:32:58 CST 1385468 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:33:28 CST 1389265 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:33:54 CST 1393148 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:34:57 CST 1395846 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:36:06 CST 1402561 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:37:11 CST 1409616 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:37:45 CST 1417253 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:38:09 CST 1422862 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:38:36 CST 1425459 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:39:09 CST 1428047 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:39:33 CST 1432979 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:39:56 CST 1435780 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:40:22 CST 1438226 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:40:55 CST 1441125 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:41:54 CST 1446153 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:43:06 CST 1452825 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:43:37 CST 1457813 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:44:02 CST 1462712 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:45:03 CST 1465609 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:45:31 CST 1472848 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:46:36 CST 1476812 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:47:03 CST 1483969 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:48:10 CST 1487659 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:48:37 CST 1495314 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:49:39 CST 1498760 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:50:06 CST 1507043 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:51:10 CST 1509977 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:52:17 CST 1517387 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:53:21 CST 1521584 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:54:32 CST 1530153 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:55:26 CST 1538506 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:55:54 CST 1544927 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:56:18 CST 1549216 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:57:22 CST 1551763 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:58:15 CST 1559986 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 05:59:22 CST 1565247 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:00:16 CST 1574059 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:01:22 CST 1581436 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:01:54 CST 1588072 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:02:52 CST 1593124 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:04:01 CST 1599488 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:05:17 CST 1608188 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:06:18 CST 1617473 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:07:26 CST 1625507 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:08:38 CST 1632651 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:09:44 CST 1641015 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:10:47 CST 1649976 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:11:50 CST 1658379 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:13:03 CST 1664763 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:14:17 CST 1673739 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:15:19 CST 1682899 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:16:12 CST 1690588 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:17:31 CST 1696582 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:18:23 CST 1703043 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:19:18 CST 1710865 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:20:32 CST 1716930 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:21:41 CST 1726188 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:22:47 CST 1734999 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:23:48 CST 1742636 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:24:42 CST 1747068 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:25:47 CST 1754959 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:26:47 CST 1758729 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:28:01 CST 1767361 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:28:53 CST 1776971 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:29:55 CST 1784804 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:31:09 CST 1788496 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:32:09 CST 1797552 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:33:07 CST 1806233 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:34:16 CST 1813554 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:35:26 CST 1821067 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:36:30 CST 1830427 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:37:38 CST 1839177 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:38:31 CST 1847343 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:39:27 CST 1853850 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:40:23 CST 1861963 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:41:23 CST 1868072 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:42:22 CST 1876224 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:43:16 CST 1884306 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:44:32 CST 1890227 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:45:23 CST 1896940 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:46:18 CST 1904751 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:47:29 CST 1910305 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:48:30 CST 1916828 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:49:13 CST 1925465 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:50:21 CST 1930183 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:51:15 CST 1937176 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:52:10 CST 1944363 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:53:22 CST 1951010 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:54:13 CST 1960708 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:55:15 CST 1967795 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:56:22 CST 1974717 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:57:21 CST 1981177 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:58:28 CST 1989448 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 06:59:31 CST 1997185 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:00:22 CST 2005729 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:01:25 CST 2013910 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:02:29 CST 2020525 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:03:19 CST 2029063 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:04:07 CST 2036458 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:05:19 CST 2040886 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:06:08 CST 2046490 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:07:03 CST 2054460 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:08:02 CST 2059977 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:09:12 CST 2064583 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:10:17 CST 2074463 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:11:25 CST 2082046 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:12:25 CST 2088919 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:13:30 CST 2097785 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:14:24 CST 2105080 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:15:12 CST 2112814 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:16:07 CST 2119859 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:16:59 CST 2126513 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:17:58 CST 2134233 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:18:54 CST 2141015 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:20:06 CST 2149077 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:20:59 CST 2153065 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:22:02 CST 2162177 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:22:54 CST 2168120 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:23:52 CST 2176557 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:24:51 CST 2183054 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:25:44 CST 2189713 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:26:33 CST 2197242 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:27:27 CST 2203518 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:28:26 CST 2212152 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:29:33 CST 2218747 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:30:37 CST 2227646 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:31:23 CST 2236932 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:32:22 CST 2240744 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:33:11 CST 2249265 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:34:05 CST 2256201 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:35:04 CST 2263311 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:35:56 CST 2272325 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:37:04 CST 2278520 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:37:55 CST 2285048 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:38:54 CST 2293316 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:40:02 CST 2298569 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:40:52 CST 2305182 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:41:38 CST 2313619 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:42:31 CST 2318536 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:43:23 CST 2327565 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:44:18 CST 2331243 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:45:09 CST 2339655 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:46:03 CST 2346444 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:46:57 CST 2351731 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:47:56 CST 2356481 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:49:05 CST 2364321 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:49:52 CST 2370919 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:50:41 CST 2378731 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:51:31 CST 2384145 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:52:24 CST 2393046 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:53:12 CST 2397857 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:54:08 CST 2405780 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:54:58 CST 2412869 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:55:51 CST 2420187 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:56:56 CST 2427557 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:57:57 CST 2433106 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:58:41 CST 2442114 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 07:59:37 CST 2448920 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:00:36 CST 2454724 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:01:20 CST 2464254 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:02:20 CST 2467638 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:03:12 CST 2474719 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:04:03 CST 2481688 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:05:01 CST 2488183 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:05:55 CST 2492854 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:06:50 CST 2501628 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:07:42 CST 2509820 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:08:38 CST 2516340 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:09:41 CST 2523513 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:10:35 CST 2533236 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:11:25 CST 2540023 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:12:14 CST 2547743 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:13:09 CST 2554185 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:14:02 CST 2561359 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:14:52 CST 2570557 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:15:49 CST 2576266 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:16:47 CST 2585145 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:17:44 CST 2593386 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:18:58 CST 2600743 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:19:58 CST 2607882 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:20:54 CST 2618032 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:21:59 CST 2625289 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:22:54 CST 2634854 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:23:58 CST 2642880 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:24:48 CST 2651289 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:25:35 CST 2659316 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:26:35 CST 2665498 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:27:34 CST 2671740 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:28:33 CST 2676746 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:29:29 CST 2686334 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:30:26 CST 2694968 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:31:14 CST 2703168 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:32:24 CST 2709329 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:33:24 CST 2718998 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:34:29 CST 2727982 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:35:43 CST 2736245 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:36:47 CST 2745524 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:37:49 CST 2754321 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:38:54 CST 2759022 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:40:03 CST 2769686 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:41:09 CST 2779134 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:42:18 CST 2789881 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:43:31 CST 2799053 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:44:49 CST 2806928 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:45:50 CST 2815827 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:46:45 CST 2825337 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:47:46 CST 2832168 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:48:59 CST 2841086 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:49:58 CST 2851904 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:51:05 CST 2862557 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:52:18 CST 2871642 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:53:31 CST 2879685 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:54:24 CST 2888318 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:55:26 CST 2895687 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:56:27 CST 2903522 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:57:27 CST 2913786 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:58:23 CST 2921328 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 08:59:30 CST 2929693 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:00:25 CST 2938177 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:01:29 CST 2946972 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:02:26 CST 2955779 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:03:23 CST 2965104 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:04:29 CST 2974112 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:05:32 CST 2982658 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:06:26 CST 2992060 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:07:27 CST 3001163 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:08:26 CST 3009045 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:09:23 CST 3018786 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:10:26 CST 3027419 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:11:28 CST 3036241 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:12:32 CST 3045566 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:13:41 CST 3053320 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:14:49 CST 3064215 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:15:52 CST 3073858 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:16:45 CST 3084584 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:17:49 CST 3092045 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:18:56 CST 3100575 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:19:58 CST 3109288 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:21:00 CST 3119488 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:22:14 CST 3128155 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:23:13 CST 3138830 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:24:14 CST 3149600 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:25:16 CST 3156313 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:26:30 CST 3165923 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:27:33 CST 3177623 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:28:41 CST 3186580 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:29:56 CST 3195390 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:30:56 CST 3203827 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:31:54 CST 3213054 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:33:03 CST 3221884 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:34:01 CST 3232147 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:34:55 CST 3241350 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:35:53 CST 3250111 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:36:56 CST 3257626 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:37:59 CST 3267072 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:39:05 CST 3276651 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:40:02 CST 3284176 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:41:12 CST 3294334 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:42:34 CST 3306003 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:43:44 CST 3315905 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:44:53 CST 3326372 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:46:10 CST 3337175 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:47:32 CST 3349550 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:48:43 CST 3361272 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:50:01 CST 3372286 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:51:15 CST 3383933 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:52:26 CST 3394874 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:53:41 CST 3405710 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:54:54 CST 3417376 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:56:05 CST 3426617 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:57:16 CST 3438341 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:58:25 CST 3448456 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 09:59:36 CST 3458777 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:00:47 CST 3469049 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:02:03 CST 3477487 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:03:11 CST 3490807 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:04:17 CST 3499704 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:05:35 CST 3510110 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:06:52 CST 3520944 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:08:07 CST 3531620 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:09:41 CST 3541990 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:11:00 CST 3557333 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:12:25 CST 3569533 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:13:57 CST 3580834 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:15:15 CST 3594208 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:16:36 CST 3606511 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:18:03 CST 3618836 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:19:24 CST 3630550 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:20:38 CST 3644346 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:21:42 CST 3656610 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:22:47 CST 3668464 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:23:56 CST 3678474 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:25:05 CST 3687466 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:26:16 CST 3699387 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:27:16 CST 3711876 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:28:26 CST 3721684 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:29:44 CST 3731979 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:30:51 CST 3740849 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:32:09 CST 3750628 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:33:11 CST 3763000 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:34:14 CST 3773619 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:35:32 CST 3784350 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:36:43 CST 3795955 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:37:59 CST 3807691 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:39:20 CST 3818355 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:40:44 CST 3829160 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:42:14 CST 3841850 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:43:30 CST 3856901 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:44:51 CST 3868928 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:46:09 CST 3880990 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:47:36 CST 3893585 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:48:58 CST 3906150 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:50:17 CST 3920615 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:51:41 CST 3935054 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:53:06 CST 3946135 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:54:16 CST 3960545 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:55:35 CST 3971237 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:56:56 CST 3985857 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:58:23 CST 3997625 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 10:59:35 CST 4012711 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:00:39 CST 4025970 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:02:02 CST 4035342 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:03:18 CST 4050572 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:04:43 CST 4063100 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:06:07 CST 4073079 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:07:11 CST 4087433 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:08:23 CST 4097213 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:09:46 CST 4109679 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:11:10 CST 4122646 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:12:32 CST 4136687 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:13:53 CST 4150568 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:15:09 CST 4163980 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:16:41 CST 4176689 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:18:12 CST 4191407 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:19:24 CST 10922 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:20:43 CST 26930 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:21:55 CST 40844 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:23:06 CST 54573 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:24:21 CST 65525 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:25:34 CST 75643 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:26:49 CST 87855 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:27:58 CST 98652 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:29:14 CST 108381 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:30:36 CST 121783 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:31:54 CST 137126 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:33:01 CST 150687 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:34:02 CST 161053 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:35:04 CST 170717 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:36:05 CST 180069 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:37:15 CST 185846 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:38:18 CST 195770 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:39:14 CST 206831 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:40:20 CST 212777 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:41:28 CST 221537 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:42:34 CST 232926 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:43:31 CST 243905 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:44:33 CST 251999 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:45:30 CST 261766 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:46:37 CST 270849 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:47:42 CST 279761 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:48:41 CST 288444 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:49:36 CST 297240 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:50:44 CST 304931 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:51:48 CST 313473 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:52:42 CST 322983 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:53:42 CST 329700 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:54:46 CST 338145 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:55:44 CST 348045 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:56:42 CST 355949 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:57:44 CST 363585 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:58:39 CST 371766 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 11:59:37 CST 380256 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:00:41 CST 388248 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:01:47 CST 396974 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:02:48 CST 405989 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:03:46 CST 413840 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:04:43 CST 424452 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:05:40 CST 431173 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:06:41 CST 438704 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:07:55 CST 444606 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:09:04 CST 453908 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:10:12 CST 463265 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:11:28 CST 472291 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:12:37 CST 484527 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:13:44 CST 496133 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:14:54 CST 505254 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:15:59 CST 514419 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:16:58 CST 524748 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:17:58 CST 532744 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:18:59 CST 540336 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:20:01 CST 550248 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:21:06 CST 557810 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:22:08 CST 567250 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:23:09 CST 576231 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:24:08 CST 584693 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:25:09 CST 592617 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:26:05 CST 602012 1001 1001 SIGABRT none /opt/pgsql/bin/postgres -
Thu 2026-06-04 12:27:05 CST 611851 1001 1001 SIGABRT present /opt/pgsql/bin/postgres 15.6M
查看 coredump 信息
shell
# 06-04 临近中午执行
[root@ums53 bak]# coredumpctl info 4076
PID: 4076 (postgres)
UID: 1001 (postgres)
GID: 1001 (postgres)
Signal: 6 (ABRT)
Timestamp: Thu 2026-06-04 02:45:22 CST (12h ago)
Command Line: $'postgres(5432): checkpointer '
Executable: /opt/pgsql/bin/postgres
Control Group: /system.slice/common-database0.service
Unit: common-database0.service
Slice: system.slice
Boot ID: a90835c07150428abd9262f01ffdfff4
Machine ID: 50b0b7a48846479ead938b328564b1fb
Hostname: ums53
Storage: /var/lib/systemd/coredump/core.postgres.1001.a90835c07150428abd9262f01ffdfff4.4076.1780512322000000.lz4 (missing)
Message: Process 4076 (postgres) of user 1001 dumped core.
# 06-04 下午执行
[root@ums53 bak]# coredumpctl info |head -100
PID: 611851 (postgres)
UID: 1001 (postgres)
GID: 1001 (postgres)
Signal: 6 (ABRT)
Timestamp: Thu 2026-06-04 12:26:10 CST (2h 48min ago)
Command Line: $'postgres(5432): checkpointer performing end-of-recovery checkpoint'
Executable: /opt/pgsql/bin/postgres
Control Group: /system.slice/common-database0.service
Unit: common-database0.service
Slice: system.slice
Boot ID: a90835c07150428abd9262f01ffdfff4
Machine ID: 50b0b7a48846479ead938b328564b1fb
Hostname: ums53
Storage: /var/lib/systemd/coredump/core.postgres.1001.a90835c07150428abd9262f01ffdfff4.611851.1780547170000000.lz4 (present)
Size on Disk: 15.6M
Message: Process 611851 (postgres) of user 1001 dumped core.
[root@ums53 bak]# ll /var/lib/systemd/coredump
total 16080
-rw-r-----+ 1 root root 16459982 Jun 4 12:27 core.postgres.1001.a90835c07150428abd9262f01ffdfff4.611851.1780547170000000.lz4
[root@ums53 bak]#
磁盘满是谁导致的

shell
[root@ums53 common-database0]# du -sh /var/log/func-AS0/StartInfo/*
1.4G /var/log/func-AS0/StartInfo/func-AS0_ops_error.log
23G /var/log/func-AS0/StartInfo/func-AS0_ops.log
这个 func-AS 组件有异常, 日志大打了 24.4G
发现是 func-AS组件日志打印过大
du -sh /var/log/func-AS0/2.0.9/ /var/log/func-AS0/StartInfo
结论:
-
可以很清楚的看到 06-04 02:45:22 出现了 postgres 进程 coredump,
-
从 06-04 10:47:34 开始报错硬盘空间不够 No space left on device .
-
对应 pg_control last modified: Thu 04 Jun 2026 10:47:42 AM CST 这个时间点
事件时间线
-
6月3日 18:54 --- 服务器重启,
pg_ctl.sh start删除了残留的postmaster.pid后启动 PostgreSQL -
6月3日 18:55 --- 启动成功,日志显示
database system was not properly shut down; automatic recovery in progress,随后完成 recovery 并正常接受连接 -
6月4日 02:40 --- 最后一次正常 checkpoint(
Time of latest checkpoint: Thu 04 Jun 2026 02:40:22 AM CST) -
6月4日 10:47 ---
pg_control状态被标记为shutting down,说明数据库收到了关闭信号但未完成关闭 -
6月4日 10:47~10:51 --- 当前状态:systemd 触发了重启(
Restart=always),PostgreSQL 进入 recovery → end-of-recovery checkpoint,但因为 系统 I/O 压力极大(负载 22+,sy% 41.8%),checkpoint 极其缓慢
根因分析
-
数据库在 6月4日凌晨 02:40 后由于磁盘空间满, 导致
pg_control状态为shutting down。重启后进入 crash recovery,end-of-recovery checkpoint 必须刷完所有脏页才能接受连接,但系统 I/O 负载过高导致 checkpoint 极其缓慢。 -
kworker内核线程和systemd-coredump进程活跃,说明可能有进程发生了 core dump,导致 I/O 风暴
AI 总结
问题1:PG 是在 shutdown 完成后的 crash recovery 阶段,还是正在准备完成 shutdown 的阶段?
答案:既不是正常的 shutdown 完成,也不是正常 shutdown 过程中。而是进入了"崩溃循环"状态。
详细分析:
**pg_controldata** 显示 **Database cluster state: shutting down** 的含义:
在 PostgreSQL 源码中,shutting down 这个状态表示 postmaster 收到了关闭信号(SIGTERM/SIGINT),并且在 pg_control 中记录了这个状态,但尚未完成 checkpoint 就异常退出了。也就是说:
-
✅ PostgreSQL 曾经收到过关闭信号
-
❌ 但没有完成正常的 shutdown 流程 (如果正常完成,状态应该是
shut down,而不是shutting down) -
❌ 进程被异常中断 (crash / kill / core dump),留下了
shutting down这个中间状态
但关键发现------进程在不断 core dump(SIGABRT)!
从 coredumpctl list 看到的证据链:
| 时间 | 事件 |
|---|---|
| 6月4日 02:45:22 | 第一个 postgres core dump(PID 4076,是 checkpointer 进程,信号 SIGABRT) |
| 6月4日 02:45:22 | 同一时间 auditd 报告磁盘空间满 |
| 6月4日 02:45:50 ~ 10:59 | 699 次 postgres core dump,每隔约 25~28 秒一次,全是 SIGABRT |
| 当前 11:00+ | startup 进程 + checkpointer 进程仍在循环 |
这意味着: PostgreSQL 当前处于一个死循环中:
plaintext
启动 → crash recovery → end-of-recovery checkpoint → 写磁盘失败(磁盘满)→
checkpointer SIGABRT → 进程崩溃 → systemd Restart=always → 重新启动 →
再次进入 crash recovery → 再次 checkpoint → 再次失败 → 再次 SIGABRT → ...
关键证据: coredumpctl info 显示最近一个 core dump 的命令行就是:
plaintext
postgres(5432): checkpointer performing end-of-recovery checkpoint
也就是说,checkpointer 在执行 end-of-recovery checkpoint 时因为磁盘空间不足 无法写入,触发了 PostgreSQL 内部的 assert 失败或 abort(),导致 SIGABRT → core dump → 重启 → 再 crash → 循环往复。
所以回答你的问题:PG 正在做 crash recovery(end-of-recovery checkpoint 阶段),但每做一次就因为磁盘满而 SIGABRT 崩溃,然后被 systemd 拉起再次尝试,形成了无限崩溃循环。
问题2:根本原因详细分析
根因链条(从最底层到最表层)
plaintext
根因①:func-AS0 日志文件失控增长(23GB 单文件)
↓
根因②:根分区磁盘 100% 满(107G 用了 106G)
↓
根因③:PostgreSQL checkpointer 无法写数据文件/WAL
↓
根因④:checkpointer 触发 SIGABRT(内部 assert/abort)
↓
根因⑤:PG 进入 crash recovery → 再次 checkpoint → 再次磁盘满 → 再次 SIGABRT
↓
现象:PG 699 次 core dump,永远无法恢复
各层证据
| 层级 | 证据 | 来源 |
|---|---|---|
| 磁盘满 | /dev/sde3 107G 106G 0 100% / |
df -h |
| 元凶文件 | func-AS0_ops.log 单文件 23GB,func-AS0_ops_error.log 1.4GB |
ls -lh /var/log/func-AS0/StartInfo/ |
| 磁盘满时刻 | 02:40:17 auditd: low on disk space → 02:45:22 auditd: no space left |
journalctl |
| 首个 core dump | 02:45:22 PID 4076 (checkpointer) SIGABRT --- 和磁盘满精确同一秒! |
coredumpctl |
| 699 次循环 | 699 个 postgres core dump,全是 SIGABRT | coredumpctl list |
| 当前仍在循环 | checkpointer 进程 5.1% 内存(1.6GB)、15.6% CPU,在做 end-of-recovery checkpoint | ps aux |
为什么 checkpointer 会 SIGABRT?
PostgreSQL 在写入数据页面时,如果 write() / fsync() 返回 ENOSPC(磁盘空间不足),行为取决于具体场景:
-
正常写入:PG 会报 ERROR 并回滚事务,不会 crash
-
checkpoint 写入 :checkpoint 是后台进程,无法"回滚事务"。如果关键数据页面无法刷盘,PG 会认为这是不可恢复的错误,调用
abort()触发 SIGABRT -
end-of-recovery checkpoint 更特殊:这是 recovery 完成后必须成功的 checkpoint,如果失败,PG 无法进入正常状态,只能崩溃重启
时间线精确还原
| 时间 | 事件 |
|---|---|
| 6月3日 18:55 | PG 正常启动,recovery 完成,开始正常服务 |
| 6月3日 18:55 ~ 6月4日 02:40 | PG 正常运行(日志有正常连接记录) |
| 6月4日 02:24 | 日志轮转(正常) |
| 6月4日 02:40 | 最后一次正常 checkpoint |
| 6月4日 02:40~02:45 | func-AS0_ops.log 迅速增长,磁盘从"low on space"变成"no space" |
| 6月4日 02:45:22 | 磁盘 100% 满 → checkpointer 写入失败 → SIGABRT → 首次 core dump |
| 6月4日 02:45:22 ~ 现在 | 崩溃循环:recovery → checkpoint → ENOSPC → SIGABRT → 重启 → 循环 |
再次梳理问题定位流程
一、磁盘满是通过哪个命令抓取到的?
直接命令: **df -h /**
bash
$ df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sde3 107G 106G 0 100% /
这就是发现磁盘 100% 满的直接命令。Use% 列是 100%,Avail 是 0。
但定位"谁吃了磁盘"是一组命令配合的:
| 步骤 | 命令 | 发现 |
|---|---|---|
| 1. 确认根分区满 | df -h / |
/dev/sde3 107G 用了 106G,100% |
| 2. 看一级目录谁最大 | du -sh /var /opt /usr /home /root /tmp |
/var 32G,/root 38G 最多 |
| 3. 深入 /var | `du -d1 -h /var/log/ | sort -rh |
| 4. 深入 func-AS0 | `du -d1 -h /var/log/func-AS0/ | sort -rh` |
| 5. 定位元凶文件 | `ls -lhS /var/log/func-AS0/StartInfo/ | head -10` |
这是核心因果链的起点。 如果没有 df -h 发现 100%,后面所有分析都找不到方向。
二、此环境中 coredump 具体怎么看?是哪里的问题?
2.1 coredump 查看三板斧
① coredumpctl list ------ 列出所有 core dump 记录
bash
$ coredumpctl list | grep postgres | wc -l
704
$ coredumpctl list | grep postgres | head -3
Thu 2026-06-04 02:45:50 CST 4076 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres
Thu 2026-06-04 02:46:18 CST 255935 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres
Thu 2026-06-04 02:46:46 CST 997257 1001 1001 SIGABRT missing /opt/pgsql/bin/postgres
关键字段解读:
| 字段 | 含义 | 本例值 |
|---|---|---|
| 时间 | core dump 发生时刻 | 从 02:45:50 一直到 11:06:07 |
| PID | 崩溃进程的 PID | 每次重启后 PID 都不同 |
| UID/GID | 进程所属用户 | 1001(postgres) |
| Signal | 致命信号 | SIGABRT(信号6)= 进程主动调用了 abort() |
| COREFILE | core 文件状态 | missing(前面几次)/ none(后面几次)= 磁盘满了写不下 |
| EXE | 崩溃的可执行文件 | /opt/pgsql/bin/postgres |
关键发现:全是 SIGABRT,不是 SIGSEGV/SIGKILL/SIGABRT 之外的其他信号。
-
SIGABRT = 信号6 :进程自己调用了
**abort()**,不是被外部 kill 的 -
如果是 SIGKILL(9) = 被外部强制杀死(如 OOM killer)
-
如果是 SIGSEGV(11) = 段错误,内存越界访问
② coredumpctl info <PID> ------ 查看某次 core dump 的详细信息
bash
# 第一次崩溃(02:45:22)
$ coredumpctl info 4076
PID: 4076 (postgres)
UID: 1001 (postgres)
GID: 1001 (postgres)
Signal: 6 (ABRT)
Timestamp: Thu 2026-06-04 02:45:22 CST (8h ago)
Command Line: postgres(5432): checkpointer ← 崩溃的是 checkpointer 进程
Executable: /opt/pgsql/bin/postgres
Control Group: /system.slice/common-database0.service
Unit: common-database0.service
Storage: .../core.postgres.1001....lz4 (missing) ← core 文件丢失(磁盘满写不下)
Message: Process 4076 (postgres) of user 1001 dumped core.
# 最近一次崩溃(11:03:25)
$ coredumpctl info 4063100
PID: 4063100 (postgres)
Signal: 6 (ABRT)
Command Line: postgres(5432): checkpointer performing end-of-recovery checkpoint
↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑
关键!在做 end-of-recovery checkpoint 时崩溃
Storage: none ← core 文件已不保存(磁盘满)
Message: Process 4063100 (postgres) of user 1001 dumped core.
两次 info 对比能看到:
-
第一次:
checkpointer(正常 checkpoint 阶段,磁盘刚满时触发) -
后续所有:
checkpointer performing end-of-recovery checkpoint(crash recovery 后的 end-of-recovery checkpoint 阶段)
这告诉我们:PG 已经进入不了正常状态了,每次重启都卡在 recovery 完成后的第一次 checkpoint。
③ coredumpctl 的 core 文件为什么是 missing/none?
bash
$ ls -lh /var/lib/systemd/coredump/
total 0
4.0K /var/lib/systemd/coredump/
core 文件目录是空的!因为:
-
磁盘 100% 满,coredump 写入失败
-
早期几条标记为
missing(尝试写了但没写完整) -
后期标记为
none(systemd 检测到磁盘满,直接放弃了)
这意味着我们无法用 **gdb** 加载 core 文件做栈回溯分析。 但从信号和命令行已经足够定位问题。
2.2 是哪里的问题?
结论:是 PostgreSQL 的 checkpointer 进程在做 checkpoint 写磁盘时,遇到 **ENOSPC**(No space left on device),内部触发了 **abort()** → SIGABRT。
逻辑推理链:
plaintext
1. 信号是 SIGABRT(不是 SIGSEGV/SIGKILL)→ 进程主动 abort()
2. 崩溃的进程是 checkpointer → 后台写磁盘的进程
3. 崩溃时间 02:45:22 = auditd 报告磁盘满的同一秒 → 磁盘满导致写入失败
4. 后续崩溃都在 "end-of-recovery checkpoint" → recovery 完成后必须做的 checkpoint 失败
5. PostgreSQL 源码逻辑:checkpoint 写数据页如果 write()/fsync() 返回 ENOSPC,
且无法回滚(后台进程无事务上下文),会调用 ExceptionError → abort()
三、完整实战分析流程(全步骤还原)
下面是如果从零开始排查这个问题的完整实战流程,我按步骤带你走:
第1步:确认 PG 当前状态
目标:PG 到底能不能用?进程在不在?
bash
# 1.1 看进程
$ ps aux | grep postgres | grep -v grep
postgres 2905 20.7 0.4 2364404 135084 ? Rs Jun03 201:22 /opt/pgsql/bin/postgres
postgres 4018 0.9 0.0 119616 8356 ? Ss Jun03 9:31 postgres(5432): logger 0
postgres 4029 0.0 0.0 119616 8356 ? Ss Jun03 0:00 postgres(5432): logger 1
postgres 4035 0.0 0.0 119616 8356 ? Ss Jun03 0:00 postgres(5432): logger 2
postgres 4073077 3.0 0.0 2364592 14788 ? Ss 11:04 0:01 postgres(5432): startup
postgres 4073079 15.7 4.6 2364516 1508696 ? Rs 11:04 0:06 postgres(5432): checkpointer performing end-of-recovery checkpoint
postgres 4073080 0.0 0.0 2364404 18756 ? Ss 11:04 0:00 postgres(5432): background writer
解读:
-
✅ 进程存在
-
⚠️ 有
startup进程 → 正在做 crash recovery -
⚠️ checkpointer 显示
performing end-of-recovery checkpoint→ recovery 完成后的 checkpoint 阶段 -
⚠️ checkpointer 占用 4.6% 内存(1.5GB) ,15.7% CPU → 正在拼命刷脏页
-
⚠️ 没有
postmaster的正常子进程(没有 autovacuum、没有 walwriter)→ 还没进入正常运行状态
bash
# 1.2 测试连接
$ export PGPASSWORD=Admin123@ ; /opt/pgsql/bin/pgsql/bin/psql -U postgres -d postgres -c 'SELECT 1'
# (预期:连不上,因为 startup/recovery 还没完成,或者连上了但很快又断了)
第2步:读 pg_controldata ------ PG 的"黑匣子"
目标:PG 自己记录的最后状态是什么?
bash
$ /opt/pgsql/bin/pgsql/bin/pg_controldata /opt/pgsql/data/pgdata/ | grep -i 'state\|checkpoint\|REDO\|modified'
关键输出:
plaintext
Database cluster state: shutting down
pg_control last modified: Thu 04 Jun 2026 11:04:48 AM CST
Time of latest checkpoint: Thu 04 Jun 2026 02:40:22 AM CST
解读:
| 字段 | 值 | 含义 |
|---|---|---|
Database cluster state |
**shutting down** |
PG 曾收到关闭信号,但未完成 shutdown 就异常退出了。如果正常完成,应该是 shut down(没有 ing) |
pg_control last modified |
11:04:48 AM |
pg_control 文件最近被修改的时间,说明此刻 PG 仍在尝试操作它 |
Time of latest checkpoint |
02:40:22 AM |
最后一次成功的 checkpoint 在凌晨 2:40。此后再也没有成功过 |
状态对照表:
| pg_controldata 状态 | 含义 |
|---|---|
shut down |
正常关闭完成 ✅ |
**shutting down** |
收到关闭信号但未完成,中途崩溃 ❌ |
in production |
正常运行中 ✅ |
in crash recovery |
正在做崩溃恢复 |
第3步:查系统日志 ------ 找到"第一声枪响"
目标:在系统层面,什么时间发生了什么?
bash
# 3.1 看 systemd 的服务日志
$ journalctl --since '2026-06-04 02:40:00' --until '2026-06-04 02:46:00' | grep -i 'space\|disk\|audit\|postgres\|core\|signal\|kill'
关键输出:
plaintext
Jun 04 02:40:17 ums53 auditd[999]: Audit daemon is low on disk space for logging
Jun 04 02:45:22 ums53 auditd[999]: Audit daemon has no space left on logging partition
Jun 04 02:45:22 ums53 auditd[999]: Audit daemon is suspending logging due to no space left on logging partition.
Jun 04 02:45:22 ums53 systemd[1]: Created slice Slice /system/systemd-coredump.
Jun 04 02:45:22 ums53 systemd[1]: Started Process Core Dump (PID 255662/UID 0).
Jun 04 02:45:50 ums53 systemd-coredump[255663]: Process 4076 (postgres) of user 1001 dumped core.
时间线证据:
| 时间 | 事件 | 意义 |
|---|---|---|
| 02:40:17 | auditd: low on disk space |
磁盘开始接近满 |
| 02:45:22 | auditd: no space left |
磁盘 100% 满 |
| 02:45:22 | systemd 开始处理 core dump | 同一秒!PG 崩溃了 |
| 02:45:50 | PID 4076 postgres core dump 确认 | checkpointer 崩溃 |
这是最关键的因果关联:磁盘满和 PG 崩溃精确在同一秒(02:45:22)。
第4步:查 coredump ------ 确认 PG 怎么崩的
目标:PG 是被 OOM kill 的?被人工 kill 的?还是自己 abort 的?
bash
# 4.1 看 core dump 总量
$ coredumpctl list | grep postgres | wc -l
704
# 4.2 看第一个和最后一个
$ coredumpctl list | grep postgres | head -1
Thu 2026-06-04 02:45:50 CST 4076 SIGABRT ← 信号6 = abort()
$ coredumpctl list | grep postgres | tail -1
Thu 2026-06-04 11:06:07 CST 999809 SIGABRT ← 还是信号6,8小时后还在崩
# 4.3 看详细信息
$ coredumpctl info 4076
Signal: 6 (ABRT)
Command Line: postgres(5432): checkpointer
$ coredumpctl info 4063100
Signal: 6 (ABRT)
Command Line: postgres(5432): checkpointer performing end-of-recovery checkpoint
解读:
| 问题 | 答案 | 证据 |
|---|---|---|
| 是不是 OOM kill? | 不是 | OOM killer 发 SIGKILL(9),这里全是 SIGABRT(6) |
| 是不是人工 kill? | 不是 | kill -9 发 SIGKILL(9),这里全是 SIGABRT(6) |
| 是不是段错误? | 不是 | 段错误发 SIGSEGV(11),这里是 SIGABRT(6) |
| 是什么? | PG 内部主动 abort() | SIGABRT = 进程自己调用 abort(),通常是 assert 失败或不可恢复错误 |
排除其他可能性的验证:
bash
# dmesg 确认没有 OOM
$ dmesg -T | grep -i 'oom\|kill\|out of memory'
# (只有无关的 PCI BAR 空间警告,没有 OOM)
第5步:查磁盘 ------ 找根因
目标:谁吃满了磁盘?
bash
# 5.1 确认磁盘满
$ df -h /
/dev/sde3 107G 106G 0 100% /
# 5.2 定位大目录
$ du -sh /var /opt /usr /home /root /tmp
32G /var
11G /opt
3.8G /usr
18G /home
38G /root
# 5.3 深入 /var/log
$ du -d1 -h /var/log/ | sort -rh | head -5
29G /var/log/
25G /var/log/func-AS0 ← 占了 86%!
# 5.4 深入 func-AS0
$ du -d1 -h /var/log/func-AS0/ | sort -rh
25G /var/log/func-AS0/StartInfo
81M /var/log/func-AS0/2026-06
# 5.5 定位元凶文件
$ ls -lhS /var/log/func-AS0/StartInfo/ | head -5
-rw-r--r-- 1 root root 23G Jun 4 11:06 func-AS0_ops.log ← 23GB!
-rw-r--r-- 1 root root 1.4G Jun 4 11:06 func-AS0_ops_error.log ← 1.4GB
根因确认: **func-AS0_ops.log** 单文件 23GB,加上 **func-AS0_ops_error.log** 1.4GB,合计约 24.4GB,吃满了根分区。
第6步:验证 PG 日志 ------ 看 PG 自己说了什么
目标:PG 自己有没有报错?
bash
# 6.1 看当前 PG 错误日志
$ cat /var/log/common-database0/pg_log/postgresql_error.log | tail -30
# 全是正常的 connection/disconnection 日志,最后时间是 2026-06-03 18:42 UTC
# 说明 02:40 之后 PG 再也没能成功写入日志(因为磁盘满)
# 6.2 看轮转后的备份日志
$ zcat /var/log/common-database0/pg_log/backuplog/postgresql_error_2026-06-04_02-24-24.log.gz | grep -ai '2026-06-04 02:4' | head -20
# (没有输出 = 02:40 之后 PG 已经无法写任何日志了)
这也佐证了磁盘满: PG 的 logger 进程连日志都写不进去了。
第7步:综合推理 ------ 形成完整因果链
把所有证据串起来:
plaintext
因果链(从底层到表象):
根因① func-AS0 组件的日志无轮转/限大小机制
func-AS0_ops.log 从某天开始持续增长,至 23GB
↓
根因② 根分区 /dev/sde3(107G)被耗尽
02:40:17 auditd 检测到磁盘空间低
02:45:22 auditd 确认磁盘完全耗尽
↓
根因③ PostgreSQL 的 checkpointer 进程无法写入数据页
write()/fsync() 返回 ENOSPC (No space left on device)
↓
根因④ checkpointer 无法回滚(后台进程无事务上下文)
PG 内部认为这是不可恢复错误,调用 abort()
→ 触发 SIGABRT → 进程崩溃
↓
根因⑤ pg_control 记录状态为 "shutting down"(收到信号但未完成关闭)
↓
根因⑥ systemd Restart=always 自动重启 PG
→ PG 进入 crash recovery
→ recovery 完成后做 end-of-recovery checkpoint
→ 写磁盘仍然失败(磁盘还是满的!)
→ 再次 SIGABRT → 再次崩溃
↓
表象 8 小时内 704 次 core dump,PG 永远无法恢复
第8步:修复
核心原则:必须先释放磁盘空间,否则 PG 永远无法恢复。
bash
# 第1步:截断元凶日志文件(不删除文件,避免进程 fd 泄漏)
> /var/log/func-AS0/StartInfo/func-AS0_ops.log
> /var/log/func-AS0/StartInfo/func-AS0_ops_error.log
# 第2步:确认磁盘空间已释放
df -h /
# 第3步:强制重启 PG(因为它在崩溃循环中)
systemctl stop common-database0
sleep 5
# 如果进程还在,强制杀
kill -9 $(pgrep -u postgres postgres) 2>/dev/null
sleep 2
# 第4步:清理残留 PID 文件
rm -f /opt/pgsql/data/pgdata/postmaster.pid
# 第5步:重新启动
systemctl start common-database0
# 第6步:等待 recovery 完成,检查连接
sleep 30
export PGPASSWORD=Admin123@ ; /opt/pgsql/bin/pgsql/bin/psql -U postgres -d postgres -c 'SELECT 1'
# 第7步:确认 pg_controldata 状态变为 in production
/opt/pgsql/bin/pgsql/bin/pg_controldata /opt/pgsql/data/pgdata/ | grep 'Database cluster state'
完整分析流程总结图
plaintext
排查入口
│
├─ 1. ps aux | grep postgres ──→ 进程在不在?什么角色?占多少资源?
│
├─ 2. pg_controldata ──→ PG 自己记录的最后状态是什么?
│ ├─ shutting down = 未完成关闭就崩了
│ ├─ in crash recovery = 正在恢复
│ └─ in production = 正常
│
├─ 3. journalctl / dmesg ──→ 系统层面发生了什么?
│ ├─ auditd 报磁盘满 ← 关键证据!
│ ├─ OOM killer? → dmesg 排除
│ └─ coredump 记录 ← 崩溃时间和信号
│
├─ 4. coredumpctl ──→ 进程怎么崩的?
│ ├─ SIGABRT(6) = 自己 abort() → 不可恢复错误
│ ├─ SIGKILL(9) = 被 kill → OOM 或人工
│ └─ SIGSEGV(11) = 段错误 → 内存越界
│
├─ 5. df -h / du -sh ──→ 磁盘为什么满?谁吃的?
│ └─ 逐层下钻:/ → /var → /var/log → func-AS0 → func-AS0_ops.log (23GB)
│
├─ 6. PG 日志 ──→ PG 自己有没有报错?
│ └─ 磁盘满后连日志都写不了 → 佐证磁盘问题
│
└─ 7. 综合推理 ──→ 串联因果链
└─ 日志失控→磁盘满→checkpoint 写失败→abort→崩溃循环