ChristopherJKoen's picture
download
raw
4.05 kB
2026-04-08 18:59:12.200 UTC [43] LOG: starting PostgreSQL 15.16 (Debian 15.16-0+deb12u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
2026-04-08 18:59:12.201 UTC [43] LOG: listening on IPv4 address "127.0.0.1", port 5432
2026-04-08 18:59:12.543 UTC [43] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2026-04-08 18:59:13.269 UTC [46] LOG: database system was shut down at 2026-04-08 18:56:44 UTC
2026-04-08 18:59:13.954 UTC [43] LOG: database system is ready to accept connections
2026-04-08 19:00:29.903 UTC [47] PANIC: could not fdatasync file "000000010000000000000001": Input/output error
2026-04-08 19:00:38.264 UTC [43] LOG: WAL writer process (PID 47) was terminated by signal 6: Aborted
2026-04-08 19:00:38.264 UTC [43] LOG: terminating any other active server processes
2026-04-08 19:00:38.269 UTC [43] LOG: all server processes terminated; reinitializing
2026-04-08 19:00:38.696 UTC [119] LOG: database system was interrupted; last known up at 2026-04-08 18:59:13 UTC
2026-04-08 19:00:41.393 UTC [169] FATAL: the database system is in recovery mode
2026-04-08 19:00:44.526 UTC [218] FATAL: the database system is in recovery mode
2026-04-08 19:00:47.651 UTC [267] FATAL: the database system is in recovery mode
2026-04-08 19:00:48.697 UTC [119] LOG: syncing data directory (pre-fsync), elapsed time: 10.00 s, current path: ./base/4/3466
2026-04-08 19:00:50.834 UTC [316] FATAL: the database system is in recovery mode
2026-04-08 19:00:53.918 UTC [365] FATAL: the database system is in recovery mode
2026-04-08 19:00:56.972 UTC [414] FATAL: the database system is in recovery mode
2026-04-08 19:00:58.718 UTC [119] LOG: syncing data directory (pre-fsync), elapsed time: 20.02 s, current path: ./base/5/2187
2026-04-08 19:01:00.023 UTC [463] FATAL: the database system is in recovery mode
2026-04-08 19:01:03.133 UTC [512] FATAL: the database system is in recovery mode
2026-04-08 19:01:06.230 UTC [561] FATAL: the database system is in recovery mode
2026-04-08 19:01:08.703 UTC [119] LOG: syncing data directory (pre-fsync), elapsed time: 30.00 s, current path: ./base/16384/2615_fsm
2026-04-08 19:01:09.325 UTC [610] FATAL: the database system is in recovery mode
2026-04-08 19:01:12.422 UTC [659] FATAL: the database system is in recovery mode
2026-04-08 19:01:15.547 UTC [708] FATAL: the database system is in recovery mode
2026-04-08 19:01:18.592 UTC [757] FATAL: the database system is in recovery mode
2026-04-08 19:01:21.703 UTC [806] FATAL: the database system is in recovery mode
2026-04-08 19:01:24.789 UTC [855] FATAL: the database system is in recovery mode
2026-04-08 19:01:27.358 UTC [119] LOG: syncing data directory (fsync), elapsed time: 10.30 s, current path: ./global/3593
2026-04-08 19:01:27.845 UTC [904] FATAL: the database system is in recovery mode
2026-04-08 19:01:30.960 UTC [953] FATAL: the database system is in recovery mode
2026-04-08 19:01:34.043 UTC [1002] FATAL: the database system is in recovery mode
2026-04-08 19:01:37.140 UTC [119] LOG: syncing data directory (fsync), elapsed time: 20.08 s, current path: ./base/1/3429
2026-04-08 19:01:37.183 UTC [1051] FATAL: the database system is in recovery mode
2026-04-08 19:01:37.447 UTC [43] LOG: received fast shutdown request
2026-04-08 19:01:47.206 UTC [119] LOG: syncing data directory (fsync), elapsed time: 30.15 s, current path: ./base/1/4154
2026-04-08 19:01:57.125 UTC [119] LOG: syncing data directory (fsync), elapsed time: 40.07 s, current path: ./base/1/2685
2026-04-08 19:02:07.170 UTC [119] LOG: syncing data directory (fsync), elapsed time: 50.11 s, current path: ./base/1/2619_fsm
2026-04-08 19:02:17.107 UTC [119] LOG: syncing data directory (fsync), elapsed time: 60.05 s, current path: ./base/4/2601
2026-04-08 19:02:27.177 UTC [119] LOG: syncing data directory (fsync), elapsed time: 70.12 s, current path: ./base/4/2835
2026-04-08 19:02:37.070 UTC [119] LOG: syncing data directory (fsync), elapsed time: 80.01 s, current path: ./base/4/2675

Xet Storage Details

Size:
4.05 kB
·
Xet hash:
dbe1129d549916db9ad34441e4990594640bafb94403c98dca4f6362fba3aed0

Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.