From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alex F <phoedos16@gmail.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16833: postgresql 13.1 process crash every hour
Date: Fri, 14 May 2021 10:57:30 -0400
Message-ID: <1884042.1621004250@sss.pgh.pa.us> (raw)
In-Reply-To: <CAGbr_zXOUzvpXZm9fi6sysw4bavUNHHBgNTCsZC9XE1zVzke1g@mail.gmail.com>
References: <16833-12d1cd7c13c78bde@postgresql.org>
<20210122175556.flvrb532anccsnca@alap3.anarazel.de>
<CAGbr_zVCq-eW+PrE4K3wJGFmqC60w27EqHsNH6+hYC=YL0EnTg@mail.gmail.com>
<CAGbr_zVNNrpDuDTi5eNYrUjg_8SQ_anggyfR6C0=Lx_3yv=jbg@mail.gmail.com>
<1060558.1620827849@sss.pgh.pa.us>
<CAGbr_zXOUzvpXZm9fi6sysw4bavUNHHBgNTCsZC9XE1zVzke1g@mail.gmail.com>
Alex F <phoedos16@gmail.com> writes:
> Think I was able to get a gdb stack trace. Logs attached.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00007ffa43a2c94d in __memmove_avx_unaligned_erms () from
> /lib64/libc.so.6
> (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 ()
Hmm, looks like it's time to rope Peter Geoghegan in on this discussion.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, phoedos16@gmail.com, pg@bowt.ie, andres@anarazel.de, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16833: postgresql 13.1 process crash every hour
In-Reply-To: <1884042.1621004250@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox