2023-10-26 05:33:04.783 UTC [1817140] LOG: database system was not properly shut down; automatic recovery in progress 2023-10-26 05:33:04.790 UTC [1817140] LOG: redo starts at 8D2/23E6F528 2023-10-26 05:33:04.791 UTC [1817140] LOG: invalid record length at 8D2/23E78380: wanted 24, got 0 2023-10-26 05:33:04.791 UTC [1817140] LOG: redo done at 8D2/23E78358 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2023-10-26 05:33:04.804 UTC [1817141] LOG: checkpoint starting: end-of-recovery immediate wait 2023-10-26 05:33:04.881 UTC [1817141] LOG: checkpoint complete: wrote 12 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.068 s, sync=0.004 s, total=0.078 s; sync files=11, longest=0.002 s, average=0.001 s; distance=35 kB, estimate=35 kB 2023-10-26 05:33:04.883 UTC [1] LOG: database system is ready to accept connections 2023-10-26 05:33:13.822 UTC [1817179] PANIC: corrupted item lengths: total 8480, available space 7552 2023-10-26 05:33:13.822 UTC [1817179] STATEMENT: delete from history_uint where itemid=877561 and ctid = any(array(select ctid from history_uint where itemid=877561 limit 10000)) 2023-10-26 05:33:13.901 UTC [1] LOG: server process (PID 1817179) was terminated by signal 6: Aborted 2023-10-26 05:33:13.901 UTC [1] DETAIL: Failed process was running: delete from history_uint where itemid=877561 and ctid = any(array(select ctid from history_uint where itemid=877561 limit 10000)) 2023-10-26 05:33:13.901 UTC [1] LOG: terminating any other active server processes 2023-10-26 05:33:13.911 UTC [1] LOG: all server processes terminated; reinitializing 2023-10-26 05:33:14.349 UTC [1817181] LOG: database system was interrupted; last known up at 2023-10-26 05:33:04 UTC 2023-10-26 05:33:14.350 UTC [1817184] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.350 UTC [1817185] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.351 UTC [1817186] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.351 UTC [1817187] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.351 UTC [1817188] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.351 UTC [1817189] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.352 UTC [1817190] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.352 UTC [1817191] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.352 UTC [1817192] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.353 UTC [1817193] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.353 UTC [1817194] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.353 UTC [1817195] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.354 UTC [1817196] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.354 UTC [1817197] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.354 UTC [1817198] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.355 UTC [1817199] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.355 UTC [1817200] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.355 UTC [1817201] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.356 UTC [1817202] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.356 UTC [1817203] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.356 UTC [1817204] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.357 UTC [1817205] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.357 UTC [1817206] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.357 UTC [1817207] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.358 UTC [1817208] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.358 UTC [1817209] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.358 UTC [1817210] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.359 UTC [1817211] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.359 UTC [1817212] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.359 UTC [1817213] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.359 UTC [1817214] FATAL: the database system is in recovery mode 2023-10-26 05:33:14.897 UTC [1817181] LOG: database system was not properly shut down; automatic recovery in progress 2023-10-26 05:33:14.904 UTC [1817181] LOG: redo starts at 8D2/23E783F8 2023-10-26 05:33:14.905 UTC [1817181] LOG: invalid record length at 8D2/23E81508: wanted 24, got 0 2023-10-26 05:33:14.905 UTC [1817181] LOG: redo done at 8D2/23E814E0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s 2023-10-26 05:33:14.918 UTC [1817182] LOG: checkpoint starting: end-of-recovery immediate wait 2023-10-26 05:33:14.995 UTC [1817182] LOG: checkpoint complete: wrote 12 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.068 s, sync=0.004 s, total=0.078 s; sync files=11, longest=0.001 s, average=0.001 s; distance=36 kB, estimate=36 kB 2023-10-26 05:33:14.999 UTC [1] LOG: database system is ready to accept connections 2023-10-26 05:33:23.747 UTC [1817227] PANIC: corrupted item lengths: total 8480, available space 7552 2023-10-26 05:33:23.747 UTC [1817227] STATEMENT: delete from history_uint where itemid=877561 and ctid = any(array(select ctid from history_uint where itemid=877561 limit 10000)) 2023-10-26 05:33:23.836 UTC [1] LOG: server process (PID 1817227) was terminated by signal 6: Aborted 2023-10-26 05:33:23.836 UTC [1] DETAIL: Failed process was running: delete from history_uint where itemid=877561 and ctid = any(array(select ctid from history_uint where itemid=877561 limit 10000)) 2023-10-26 05:33:23.837 UTC [1] LOG: terminating any other active server processes 2023-10-26 05:33:23.849 UTC [1] LOG: all server processes terminated; reinitializing 2023-10-26 05:33:24.304 UTC [1817248] LOG: database system was interrupted; last known up at 2023-10-26 05:33:14 UTC 2023-10-26 05:33:24.305 UTC [1817251] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.352 UTC [1817252] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.353 UTC [1817253] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.354 UTC [1817254] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.355 UTC [1817255] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.356 UTC [1817256] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.359 UTC [1817257] FATAL: the database system is in recovery mode 2023-10-26 05:33:24.829 UTC [1817248] LOG: database system was not properly shut down; automatic recovery in progress 2023-10-26 05:33:24.837 UTC [1817248] LOG: redo starts at 8D2/23E81580 2023-10-26 05:33:24.849 UTC [1817248] LOG: unexpected pageaddr 8D1/C7000000 in log segment 00000001000008D200000024, offset 0 2023-10-26 05:33:24.849 UTC [1817248] LOG: redo done at 8D2/23FFC810 system usage: CPU: user: 0.00 s, system: 0.01 s, elapsed: 0.01 s 2023-10-26 05:33:24.860 UTC [1817249] LOG: checkpoint starting: end-of-recovery immediate wait 2023-10-26 05:33:24.940 UTC [1817249] LOG: checkpoint complete: wrote 230 buffers (0.0%); 0 WAL file(s) added, 1 removed, 0 recycled; write=0.068 s, sync=0.006 s, total=0.083 s; sync files=28, longest=0.002 s, average=0.001 s; distance=1530 kB, estimate=1530 kB 2023-10-26 05:33:24.944 UTC [1] LOG: database system is ready to accept connections