Postgres 13 signal 11: Segmentation fault tested on 2 independent machines

Hi,
first time segmentation fault happened on my laptop:

cat /etc/redhat-release 
Fedora release 32 (Thirty Two)

SELECT version();
                                                 version                                                  
----------------------------------------------------------------------------------------------------------
 PostgreSQL 13.0 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 10.2.1
20200723 (Red Hat 10.2.1-1), 64-bit


while executing SQL function:
SELECT * FROM vacuum_dead_size(now());
server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.


Please don't look at the timestamps as i was executing the function many
times. Although if you want the exact times i can also provide it.

Postgres logs:

2020-10-18 21:26:08.871 CEST [1423] LOG:  server process (PID 435031) was
terminated by signal 11: Segmentation fault
2020-10-18 21:26:08.871 CEST [1423] DETAIL:  Failed process was running:
SELECT * FROM vacuum_dead_size(now());
2020-10-18 21:26:08.871 CEST [1423] LOG:  terminating any other active
server processes
2020-10-18 21:26:08.871 CEST [429052] WARNING:  terminating connection
because of crash of another server process
2020-10-18 21:26:08.871 CEST [429052] DETAIL:  The postmaster has commanded
this server process to roll back the current transaction and exit, because
another server process exited abnormally and possibly corrupted shared
memory.
2020-10-18 21:26:08.871 CEST [429052] HINT:  In a moment you should be able
to reconnect to the database and repeat your command.
2020-10-18 21:26:08.872 CEST [428785] WARNING:  terminating connection
because of crash of another server process
2020-10-18 21:26:08.872 CEST [428785] DETAIL:  The postmaster has commanded
this server process to roll back the current transaction and exit, because
another server process exited abnormally and possibly corrupted shared
memory.
2020-10-18 21:26:08.872 CEST [428785] HINT:  In a moment you should be able
to reconnect to the database and repeat your command.
2020-10-18 21:26:08.878 CEST [435117] FATAL:  the database system is in
recovery mode
2020-10-18 21:26:08.879 CEST [1423] LOG:  all server processes terminated;
reinitializing
2020-10-18 21:26:08.911 CEST [435119] LOG:  database system was interrupted;
last known up at 2020-10-18 21:23:52 CEST
2020-10-18 21:26:08.977 CEST [435119] LOG:  database system was not properly
shut down; automatic recovery in progress
2020-10-18 21:26:08.980 CEST [435119] LOG:  redo starts at 0/E5080E8
2020-10-18 21:26:08.981 CEST [435119] LOG:  invalid record length at
0/E540EA8: wanted 24, got 0
2020-10-18 21:26:08.981 CEST [435119] LOG:  redo done at 0/E540E80
2020-10-18 21:26:09.000 CEST [1423] LOG:  database system is ready to accept
connections


journalctl:

Oct 18 20:48:48 localhost.localdomain systemd-coredump[428779]: Process
428774 (postmaster) of user 26 dumped core.
                                                                
                                                                Stack trace
of thread 428774:
                                                                #0 
0x00007fcbbbdd06e8 __memmove_avx_unaligned_erms (libc.so.6 + 0x1656e8)
                                                                #1 
0x00000000004f8362 fill_val (postgres + 0xf8362)
                                                                #2 
0x00000000004f908d heap_fill_tuple (postgres + 0xf908d)
                                                                #3 
0x00000000004fa27b heap_form_minimal_tuple (postgres + 0xfa27b)
                                                                #4 
0x000000000067c509 tts_minimal_materialize (postgres + 0x27c509)
                                                                #5 
0x000000000067c558 tts_minimal_copy_minimal_tuple (postgres + 0x27c558)
                                                                #6 
0x0000000000918ba7 tuplestore_puttupleslot (postgres + 0x518ba7)
                                                                #7 
0x000000000067f5c3 sqlfunction_receive (postgres + 0x27f5c3)
                                                                #8 
0x0000000000671f4f standard_ExecutorRun (postgres + 0x271f4f)
                                                                #9 
0x00000000006805b4 fmgr_sql (postgres + 0x2805b4)
                                                                #10
0x000000000067a4bf ExecMakeTableFunctionResult (postgres + 0x27a4bf)
                                                                #11
0x000000000068a2b1 FunctionNext (postgres + 0x28a2b1)
                                                                #12
0x0000000000671f22 standard_ExecutorRun (postgres + 0x271f22)
                                                                #13
0x00000000007d439c PortalRunSelect (postgres + 0x3d439c)
                                                                #14
0x00000000007d56ee PortalRun (postgres + 0x3d56ee)
                                                                #15
0x00000000007d127c exec_simple_query (postgres + 0x3d127c)
                                                                #16
0x00000000007d32e9 PostgresMain (postgres + 0x3d32e9)
                                                                #17
0x000000000075d569 ServerLoop (postgres + 0x35d569)
                                                                #18
0x000000000075e4b3 PostmasterMain (postgres + 0x35e4b3)
                                                                #19
0x00000000004f03f3 main (postgres + 0xf03f3)
                                                                #20
0x00007fcbbbc92042 __libc_start_main (libc.so.6 + 0x27042)
                                                                #21
0x00000000004f049e _start (postgres + 0xf049e)








--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html