Обсуждение: re: constant crashing
Here is an excerpt of /var/log/postgresql/postgresql-16-main.log
2024-04-14 12:17:42.321 EDT [7124] LOG: checkpoint starting: wal
Should I increase the max_wal_size to 2GB ?
2024-04-14 12:17:43.153 EDT [1227] LOG: server process (PID 7289) was terminated by signal 11: Segmentation fault
2024-04-14 12:17:43.153 EDT [1227] DETAIL: Failed process was running: UPDATE main SET category_modified = UPPER(category), sub_category=UPPER(sub_category), code1=UPPER(code1), code2=UPPER(code2);
2024-04-14 12:17:43.153 EDT [1227] LOG: terminating any other active server processes
2024-04-14 12:17:43.166 EDT [1227] LOG: all server processes terminated; reinitializing
2024-04-14 12:17:43.206 EDT [7320] LOG: database system was interrupted; last known up at 2024-04-14 12:17:42 EDT
2024-04-14 12:17:43.484 EDT [7320] LOG: database system was not properly shut down; automatic recovery in progress
2024-04-14 12:17:43.487 EDT [7320] LOG: redo starts at 1260/66400608
2024-04-14 12:17:44.985 EDT [7320] LOG: unexpected pageaddr 1260/4A7CA000 in WAL segment 00000001000012600000008C, LSN 1260/8C7CA000, offset 8167424
2024-04-14 12:17:44.986 EDT [7320] LOG: redo done at 1260/8C7C9F50 system usage: CPU: user: 1.20 s, system: 0.28 s, elapsed: 1.49 s
2024-04-14 12:17:44.999 EDT [7321] LOG: checkpoint starting: end-of-recovery immediate wait
2024-04-14 12:17:45.251 EDT [7321] LOG: checkpoint complete: wrote 16284 buffers (99.4%); 0 WAL file(s) added, 0 removed, 38 recycled; write=0.082 s, sync=0.143 s, total=0.252 s; sync files=6, longest=0.075 s, average=0.024 s; distance=626470 kB, estimate=626470 kB; lsn=1260/8C7CA048, redo lsn=1260/8C7CA048
2024-04-14 12:17:45.264 EDT [1227] LOG: database system is ready to accept connections
2024-04-14 12:28:32.526 EDT [7321] LOG: checkpoint starting: wal
2024-04-14 12:28:45.066 EDT [7321] LOG: checkpoint complete: wrote 12 buffers (0.1%); 0 WAL file(s) added, 0 removed, 33 recycled; write=12.371 s, sync=0.144 s, total=12.541 s; sync files=11, longest=0.121 s, average=0.013 s; distance=536816 kB, estimate=617505 kB; lsn=1260/CB4790B8, redo lsn=1260/AD406208
2024-04-14 12:28:45.887 EDT [7321] LOG: checkpoints are occurring too frequently (13 seconds apart)
2024-04-14 12:28:45.887 EDT [7321] HINT: Consider increasing the configuration parameter "max_wal_size".
2024-04-14 12:28:45.887 EDT [7321] LOG: checkpoint starting: wal
Should I increase the max_wal_size to 2GB ?
jack <jack4pg@a7q.com> writes: > Here is an excerpt of /var/log/postgresql/postgresql-16-main.log > 2024-04-14 12:17:43.153 EDT [1227] LOG: server process (PID 7289) was terminated by signal 11: Segmentation fault That's pretty interesting; it suggests an actual PG bug. Can you get a stack trace from that? See https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend Also, it's probably time you showed us the complete DDL definition for the tables you're working with. It's fairly hard to believe this would happen without something rather out-of-the-ordinary in the definitions. Or ... do you have any PG extensions installed? regards, tom lane
On 4/14/24 12:22, jack wrote: > Here is an excerpt of /var/log/postgresql/postgresql-16-main.log Where and how are the CSV files being produced? What is the database locale? -- Adrian Klaver adrian.klaver@aklaver.com