BUG #16578: When making an insert, the database goes to recover mode - Mailing list pgsql-bugs

The following bug has been logged on the website:

Bug reference:      16578
Logged by:          Ali Kemal Demirci
Email address:      demirci.alikemal@gmail.com
PostgreSQL version: 12.3
Operating system:   Centos
Description:

Create table xxx
Select ....
Limit 80000;

When this script is run, we get the following error.
But when we run it as "Limit 70000", it can do it successfully.
Can you help me?

2020-08-12 10:37:18.676 +03 [94157] LOG:  server process (PID 5175) was
terminated by signal 11: Segmentation fault
2020-08-12 10:37:18.676 +03 [94157] DETAIL:  Failed process was running:
create table cs_subscriber_ as
        select r.id_abone id, 1::numeric corporation_id, r.id_abone
subscriber_number, 1::numeric area_id, r.abone_tipi subscriber_type_id,
r.id_abone_adres_uavt building_flat_id, null::varchar description,
              r.creuser created_user_id, r.credate created_timestamp,
0::numeric "version", null::numeric evaluate_project_id, r.address
address_description
        from (select a.id_abone, a.abone_no, nvl(x.id_abone_tipi, 1)
abone_tipi, a.id_abone_adres_uavt, bf.building_door_id,
                      nvl(a.creuser,1::numeric) creuser , nvl(a.credate,
'01/01/1900 00:00:00'::timestamp) credate, (a.a4_adr1 ||a.a4_adr2
||a.a4_adr3)::varchar address,
                      mmp.id meter_model, a.sayac_no, a.sayac_konum,
a.sayac_takma_tarihi, a.sayac_uretim_tarihi, to_char(a.sayac_uretim_tarihi,
'yyyy')::numeric uretim_yili,
                      a.sayac_karttipi_adi, a.kart_sayac_mrk ,
a.kart_sayac_no , a.kart_sayac_seri, a.sayac_konum, a.kayit_tarihi,
a.aciklama, a.iptal_tarih,
                      ('1'||lpad(a.defter_no::tex
2020-08-12 10:37:18.676 +03 [94157] LOG:  terminating any other active
server processes
2020-08-12 10:37:18.676 +03 [5174] WARNING:  terminating connection because
of crash of another server process
2020-08-12 10:37:18.676 +03 [5174] 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-08-12 10:37:18.676 +03 [5174] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-08-12 10:37:18.676 +03 [5151] WARNING:  terminating connection because
of crash of another server process
2020-08-12 10:37:18.676 +03 [5151] 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-08-12 10:37:18.676 +03 [5151] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-08-12 10:37:18.676 +03 [5172] WARNING:  terminating connection because
of crash of another server process
2020-08-12 10:37:18.676 +03 [5172] 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-08-12 10:37:18.676 +03 [5172] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-08-12 10:37:18.676 +03 [5146] WARNING:  terminating connection because
of crash of another server process
2020-08-12 10:37:18.676 +03 [5146] 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-08-12 10:37:18.676 +03 [5146] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-08-12 10:37:18.676 +03 [5173] WARNING:  terminating connection because
of crash of another server process
2020-08-12 10:37:18.676 +03 [5173] 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-08-12 10:37:18.676 +03 [5173] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-08-12 10:37:18.677 +03 [5163] WARNING:  terminating connection because
of crash of another server process
2020-08-12 10:37:18.677 +03 [5163] 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-08-12 10:37:18.677 +03 [5163] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-08-12 10:37:18.680 +03 [94157] LOG:  all server processes terminated;
reinitializing
2020-08-12 10:37:18.704 +03 [5178] LOG:  database system was interrupted;
last known up at 2020-08-12 10:37:04 +03
2020-08-12 10:37:18.753 +03 [5179] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.819 +03 [5180] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.896 +03 [5181] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.957 +03 [5182] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.965 +03 [5183] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.975 +03 [5184] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.985 +03 [5185] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:18.994 +03 [5186] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.002 +03 [5187] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.012 +03 [5188] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.023 +03 [5189] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.038 +03 [5190] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.056 +03 [5191] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.073 +03 [5192] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.081 +03 [5193] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.095 +03 [5178] LOG:  database system was not properly
shut down; automatic recovery in progress
2020-08-12 10:37:19.095 +03 [5194] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.105 +03 [5178] LOG:  redo starts at EC/81307FF8
2020-08-12 10:37:19.114 +03 [5195] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.124 +03 [5196] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.134 +03 [5197] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.146 +03 [5204] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.151 +03 [5205] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.162 +03 [5206] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.174 +03 [5207] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.181 +03 [5208] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.186 +03 [5209] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.196 +03 [5210] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.196 +03 [5178] LOG:  redo done at EC/82131E88
2020-08-12 10:37:19.209 +03 [5211] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.218 +03 [5212] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.225 +03 [5213] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.244 +03 [5214] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.257 +03 [5215] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.265 +03 [5216] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.270 +03 [5217] FATAL:  the database system is in
recovery mode
2020-08-12 10:37:19.275 +03 [94157] LOG:  database system is ready to accept
connections
2020-08-12 10:37:19.279 +03 [5223] LOG:  pg_cron scheduler started