Re: BUG #16833: postgresql 13.1 process crash every hour

Dear Tom,
Think I was able to get a gdb stack trace. Logs attached.

PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 7.3.1
20180712 (Red Hat 7.3.1-12), 64-bit)

2021-05-14 06:10:54 UTC [22258]: user=,db=,app=,client= LOG: server
process (PID 22273) was terminated by signal 11: Segmentation fault
2021-05-14 06:10:54 UTC [22258]: user=,db=,app=,client= DETAIL: Failed
process was running: REFRESH MATERIALIZED VIEW CONCURRENTLY
project.product_master_mv
2021-05-14 06:10:54 UTC [22258]: user=,db=,app=,client= LOG: terminating
any other active server process

sudo -u postgres gdb -q -c
/usr/local/pgsql/data/core.postgres.22273.pg13_testdb.1620972642
/usr/local/pgsql/bin/postgres
Reading symbols from /usr/local/pgsql/bin/postgres...(no debugging symbols
found)...done.
[New LWP 22273]

warning: Corrupted shared library list: 0x7ffa44ed0680 != 0x68000000000021f
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `postgres: servlet staging 172.31.35.223(23762)
REFRESH MATER'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007ffa43a2c94d in __memmove_avx_unaligned_erms () from
/lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
glibc-2.26-41.amzn2.x86_64 keyutils-libs-1.5.8-3.amzn2.0.2.x86_64
krb5-libs-1.15.1-37.amzn2.2.2.x86_64 libcom_err-1.42.9-19.amzn2.x86_64
libselinux-2.5-12.amzn2.0.2.x86_64 openssl-libs-1.0.2k-19.amzn2.0.6.x86_64
pcre-8.32-17.amzn2.0.2.x86_64 zlib-1.2.7-18.amzn2.x86_64
(gdb) bt
#0 0x00007ffa43a2c94d in __memmove_avx_unaligned_erms () from
/lib64/libc.so.6
#1 0x00000000004d67f5 in _bt_swap_posting ()
#2 0x00000000004d792e in _bt_insertonpg ()
#3 0x00000000004d9113 in _bt_doinsert ()
#4 0x00000000004dc1a1 in btinsert ()
#5 0x000000000060fa7f in ExecInsertIndexTuples ()
#6 0x0000000000637078 in ExecInsert ()
#7 0x00000000006379c7 in ExecModifyTable ()
#8 0x00000000006107dc in standard_ExecutorRun ()
#9 0x0000000000645695 in _SPI_execute_plan ()
#10 0x0000000000645a3c in SPI_execute ()
#11 0x00000000005c39ff in ExecRefreshMatView ()
#12 0x000000000075799d in ProcessUtilitySlow.isra.4 ()
#13 0x00000000007567ce in standard_ProcessUtility ()
#14 0x0000000000754382 in PortalRunUtility ()
#15 0x0000000000754d4d in PortalRunMulti ()
#16 0x0000000000755763 in PortalRun ()
#17 0x000000000075330b in PostgresMain ()
#18 0x00000000006e2d8a in ServerLoop ()
#19 0x00000000006e3df7 in PostmasterMain ()
#20 0x00000000004883c2 in main ()

Thanks for your support!

ср, 12 мая 2021 г. в 18:57, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Alex F <phoedos16(at)gmail(dot)com> writes:
> > Dear team, previously I wrote about postgresql crash (ref #16833)
> > Unfortunately the issue is still present.
>
> You still haven't provided a stack trace ... there is not much we
> can do with the amount of information here.
>
> regards, tom lane
>