BUG #17229: Segmentation Fault after upgrading to version 13

The following bug has been logged on the website:

Bug reference:      17229
Logged by:          Efrain Berdecia
Email address:      ejberdecia@yahoo.com
PostgreSQL version: 13.1
Operating system:   Linux  3.10.0-1160.11.1
Description:

Ever since we upgraded to PostgreSQL version 13 we are sporadically getting
segmentation faults for the following process and all existing connections
get killed and our streaming replication process goes down. The sql below
does establish a dblink to a Greenplum cluster. For reference, this is our
log_line_prefix value;
                                  log_line_prefix
------------------------------------------------------------------------------------
 %t [%p]: [%v]-[%x] [%l-1]
cluster_name=campaign_service,user=%u,db=%d,hostname=%r


2021-10-13 03:45:24 UTC [31961]: []-[0] [1-1]
cluster_name=campaign_service,user=[unknown],db=[unknown],hostname=10.110.181.113(65011)
LOG:  connection received: host=10.110.181.113 port=65011
2021-10-13 03:45:24 UTC [31961]: [37/1745]-[0] [2-1]
cluster_name=campaign_service,user=repmgr,db=[unknown],hostname=10.110.181.113(65011)
FATAL:  no pg_hba.conf entry for replication connection from host
"10.110.181.113", user "repmgr", SSL off
2021-10-13 08:00:08 UTC [31961]: []-[0] [1-1]
cluster_name=campaign_service,user=[unknown],db=[unknown],hostname=10.110.149.59(46724)
LOG:  connection received: host=10.110.149.59 port=46724
2021-10-13 08:00:08 UTC [31961]: [52/9474]-[0] [2-1]
cluster_name=campaign_service,user=generic_toolkit_utility,db=bi_tools,hostname=10.110.149.59(46724)
LOG:  connection authorized: user=generic_toolkit_utility
database=bi_tools
2021-10-13 08:01:12 UTC [31961]: [52/0]-[0] [3-1]
cluster_name=campaign_service,user=generic_toolkit_utility,db=bi_tools,hostname=10.110.149.59(46724)
LOG:  duration: 63946.616 ms  statement:
            SELECT dblink_connect('gp_metadata_gpso','greenplum_gpso');

            SELECT dblink_exec('gp_metadata_gpso', 'SET statement_timeout =
90000');

            SET statement_timeout = 600000;

            SELECT gp_metadata.load_functions('gp_metadata_gpso');
            SELECT gp_metadata.load_tables('gp_metadata_gpso');
            SELECT gp_metadata.load_views('gp_metadata_gpso');
            SELECT gp_metadata.load_columns('gp_metadata_gpso');
            SELECT gp_metadata.load_dependencies('gp_metadata_gpso');

            SELECT
gp_metadata.load_from_tmp_to_main('functions','gp_metadata_gpso');
            SELECT
gp_metadata.load_from_tmp_to_main('tables','gp_metadata_gpso');
            SELECT
gp_metadata.load_from_tmp_to_main('views','gp_metadata_gpso');
            SELECT
gp_metadata.load_from_tmp_to_main('dependencies','gp_metadata_gpso');
            SELECT
gp_metadata.load_from_tmp_to_main('columns','gp_metadata_gpso');

            SELECT dblink_disconnect('gp_metadata_gpso');

            SELECT gp_metadata.load_all_objects('gp_metadata_gpso');
            SELECT
gp_metadata.load_from_tmp_to_main('all_objects','gp_metadata_gpso');

            UPDATE gp_metadata.status SET last_update=NOW() WHERE
enviroment='gp_metadata_gpso';
2021-10-13 08:01:36 UTC [59543]: []-[0] [248-1]
cluster_name=campaign_service,user=,db=,hostname= LOG:  server process (PID
31961) was terminated by signal 11: Segmentation fault

Here are the /var/log/messages corresponding entries;
Oct 13 08:01:36 dtord00pgm39p.dc.dotomi.net kernel: traps: postgres[31961]
general protection ip:7ff03e003140 sp:7fff3d87cd58 error:0 in
libc-2.17.so[7ff03deac000+1c4000]
Oct 13 08:01:36 dtord00pgm39p.dc.dotomi.net kernel: [12628017.578633] traps:
postgres[31961] general protection ip:7ff03e003140 sp:7fff3d87cd58 error:0
in libc-2.17.so[7ff03deac000+1c4000]

In other occasions we do see the following messages in /var/log/messages;
Oct 12 22:01:37 dtord00pgm39p.dc.dotomi.net kernel: postgres[14751]:
segfault at 204 ip 00007ff03e003140 sp 00007fff3d87d038 error 4 in
libc-2.17.so[7ff03deac000+1c4000]
Oct 12 22:01:37 dtord00pgm39p.dc.dotomi.net kernel: [12592102.529977]
postgres[14751]: segfault at 204 ip 00007ff03e003140 sp 00007fff3d87d038
error 4 in libc-2.17.so[7ff03deac000+1c4000]