"ERROR","58M01","Error on receive from seg2 10.10.x.x:50002 pid=117634: server closed the connection unexpectedly

2026-02-10 09:35:09.238016 CST,"MonitorProd","gpafiniti",p16629,th-1453139776,"10.10.x.x","46070",2026-02-10 06:00:00 CST,0,con701,cmd11,seg-1,,,,sx1,"ERROR","58M01","Error on receive from seg2 10.10.247.112:50002 pid=117634: server closed the connection unexpectedly
2026-02-10 09:35:09.244500 CST,"MonitorProd","gpafiniti",p8967,th-1453139776,"10.10.x.x","49374",2026-02-10 05:47:01 CST,0,con690,cmd120,seg-1,,,,sx1,"ERROR","58M01","Error on receive from seg2 10.10.x.x:50002 pid=113821: server closed the connection unexpectedly
2026-02-10 09:35:59.949836 CST,"MonitorProd","gpafiniti",p11017,th-1453139776,"10.10.x.x","56076",2026-02-10 05:50:00 CST,0,con700,cmd27,seg-1,,,,sx1,"ERROR","58M01","Error on receive from seg2 10.10.x.x:50002 pid=117479: server closed the connection unexpectedly

Feb 10 12:23:51 MX-CB kernel: postgres[242777]: segfault at 349d8 ip 00007f2b71c50956 sp 00007ffd2b7c3610 error 4 in libgcc_s-11-20240719.so.1[7f2b71c42000+14000] likely on CPU 14 (core 6, socket 1)

Same query executes successfully for 1-2 executions but fails in next execution with above error

Begin with the supplied receive errors and kernel segfault report, then reproduce the same query across repeated executions while collecting the failing segment and process details. No source file or test is identified in the issue; done means identifying and fixing the cause of the segment crash and verifying that repeated executions no longer close the connection.

Written by the indexing model from the issue text.