<div>Merhabalar,</div><div> </div><div>1. Hangi PostgreSQL versiyonunu kullanıyorsunuz?</div><div>2. Sistem kaynakları nedir?</div><div>3. Yapılandırma ayalarınızı paylaşır mısınız.</div><div>4. Veritabanında hangi eklentileri kullanıyorsunuz?</div><div>5. Explain ile planı alarak paylaşır mısınız.</div><div> </div><div>En önemli soru 4. soru. Veritabanı <font face="monospace">"Segmentation fault"<span style="font-family:'arial' , sans-serif"> ile kapanıyor loglarınıza göre. Veritabanı bellek alamadım diye sonlanmıyor, sistem kaynaklarının yetersizliği ile alakalı olduğunu düşünmüyorum. Veritabanı süreçlerinden birisi, kendisine ait olmayan bir bellek alanını okumaya ya da yazmaya çalışıyor. Bu da en sık C ile yazılmış bir fonksiyonun/eklentinin içerisindeki hatalı bellek yönetiminden veya kodun içerisindeki buglardan kaynaklanır.</span></font></div><div> </div><div><font face="monospace"><span style="font-family:'arial' , sans-serif">Loglardan ilk gözüme çarpan pg_cron kullandığınız. Onu kaldırmayı deneyebilirsiniz. </span></font>local_preload_libraries, session_preload_libraries ve shared_preload_libraries<font face="monospace"><span style="font-family:'arial' , sans-serif"> parametrelerinin değerlerini de kontrol ederseniz iyi olur.</span></font></div><div> </div><div><font face="monospace"><span style="font-family:'arial' , sans-serif">show </span></font>session_preload_libraries;</div><div>show shared_preload_libraries;</div><div>show local_preload_libraries;</div><div>Best regards.</div><div>Samed YILDIRIM</div><div> </div><div> </div><div> </div><div>12.08.2020, 12:17, "Ali Kemal DEMIRCI" <demirci(dot)alikemal(at)gmail(dot)com>:</div><blockquote><div><div><font face="monospace">Merhaba arkadaşlar,</font></div><div> </div><font face="monospace">Create table xxx as</font><div><font face="monospace">Select ....</font></div><div><font face="monospace">Limit 80000;</font></div><div> </div><div>Yukardaki SQL komutunu çalıştırdığımda aşağıdaki hatayı alıyorum;</div><div> </div><div><font face="monospace">SQL Error [08006]: An I/O error occurred while sending to the backend.</font></div><div> </div><div>Fakat "Limit 70000" yaptığımda başarılı şekilde select ifadesinden dönen kayıtlarla tablo oluşturulabiliyor.</div><div> </div><div>Hat oluştuğunda log dosyasında oluşan kayıtlar aşağıdaki gibidir.</div><div>Bu konuda yardımcı olabilirmisiniz?</div><div> </div><div><font face="monospace">2020-08-12 11:08:58.037 +03 [94157] LOG: server process (PID 6072) was terminated by signal 11: Segmentation fault<br />2020-08-12 11:08:58.037 +03 [94157] DETAIL: Failed process was running: create table cs_subscriber_ as<br /> 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, <br /> r.creuser created_user_id, r.credate created_timestamp, 0::numeric "version", r.address address_description<br /> 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,<br /> 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,<br /> <a href="http://mmp.id/">mmp.id</a> 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,<br /> 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,<br /> ('1'||lpad(a.defter_no::tex<br />2020-08-12 11:08:58.037 +03 [94157] LOG: terminating any other active server processes<br />2020-08-12 11:08:58.038 +03 [6074] WARNING: terminating connection because of crash of another server process<br />2020-08-12 11:08:58.038 +03 [6074] 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.<br />2020-08-12 11:08:58.038 +03 [6074] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />2020-08-12 11:08:58.038 +03 [6030] WARNING: terminating connection because of crash of another server process<br />2020-08-12 11:08:58.038 +03 [6030] 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.<br />2020-08-12 11:08:58.038 +03 [6030] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />2020-08-12 11:08:58.038 +03 [6073] WARNING: terminating connection because of crash of another server process<br />2020-08-12 11:08:58.038 +03 [6073] 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.<br />2020-08-12 11:08:58.038 +03 [6073] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />2020-08-12 11:08:58.038 +03 [6075] WARNING: terminating connection because of crash of another server process<br />2020-08-12 11:08:58.038 +03 [6075] 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.<br />2020-08-12 11:08:58.038 +03 [6075] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />2020-08-12 11:08:58.038 +03 [6056] WARNING: terminating connection because of crash of another server process<br />2020-08-12 11:08:58.038 +03 [6056] 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.<br />2020-08-12 11:08:58.038 +03 [6056] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />2020-08-12 11:08:58.038 +03 [6022] WARNING: terminating connection because of crash of another server process<br />2020-08-12 11:08:58.038 +03 [6022] 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.<br />2020-08-12 11:08:58.038 +03 [6022] HINT: In a moment you should be able to reconnect to the database and repeat your command.<br />2020-08-12 11:08:58.041 +03 [94157] LOG: all server processes terminated; reinitializing<br />2020-08-12 11:08:58.066 +03 [6086] LOG: database system was interrupted; last known up at 2020-08-12 11:08:46 +03<br />2020-08-12 11:08:58.093 +03 [6087] FATAL: the database system is in recovery mode<br />2020-08-12 11:08:58.373 +03 [6088] FATAL: the database system is in recovery mode<br />2020-08-12 11:08:58.415 +03 [6089] FATAL: the database system is in recovery mode<br />2020-08-12 11:08:58.449 +03 [6090] FATAL: the database system is in recovery mode<br />2020-08-12 11:08:58.493 +03 [6086] LOG: database system was not properly shut down; automatic recovery in progress<br />2020-08-12 11:08:58.504 +03 [6086] LOG: redo starts at EC/8764F088<br />2020-08-12 11:08:58.600 +03 [6086] LOG: invalid record length at EC/88476D80: wanted 24, got 0<br />2020-08-12 11:08:58.600 +03 [6086] LOG: redo done at EC/88476CB8<br />2020-08-12 11:08:58.675 +03 [94157] LOG: database system is ready to accept connections<br />2020-08-12 11:08:58.679 +03 [6101] LOG: pg_cron scheduler started</font><div> </div>--<div>Saygılarımla,<br /><br />Ali Kemal DEMİRCİ</div></div></div></blockquote>