You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2026-11-17 11:28:41.567954 -03,,,p9199,th-1662871360,,,,0,,,seg-1,,,,,"LOG","00000","server process (PID 2396055) was terminated by signal 6: Aborted","Failed process was running: SELECT applied_schema.vgx_tfn_sp_hourlyalert_v6();",,,,,,0,,"postmaster.c",4280,
2026-11-17 11:28:41.568034 -03,,,p9199,th-1662871360,,,,0,,,seg-1,,,,,"LOG","00000","terminating any other active server processes",,,,,,,0,,"postmaster.c",3995,
2026-11-17 11:28:41.618693 -03,,,p511961,th-1662871360,,,,0,,,seg-1,,,,,"LOG","00000","ic-proxy: received signal 3",,,,,,,0,,"ic_proxy_main.c",484,
2026-11-17 11:28:41.632571 -03,,,p511961,th-1662871360,,,,0,,,seg-1,,,,,"LOG","00000","ic-proxy: server closing",,,,,,,0,,"ic_proxy_main.c",585,
2026-11-17 11:28:41.632662 -03,,,p511961,th-1662871360,,,,0,,,seg-1,,,,,"LOG","00000","ic-proxy: server closed with code 1",,,,,,,0,,"ic_proxy_main.c",599,
2026-11-17 11:28:41.697874 -03,"u_tfnvgx_aai_da_user","gpafiniti",p2199582,th-1662871360,"192.168.30.12","51240",2026-11-16 21:30:04 -03,872117,con11658,cmd5,seg-1,,dx5163801,x872117,sx1,"LOG","08006","could not send data to client: Broken pipe",,,,,,"SELECT applied_schema.vgx_tfn_sp_hourlyalert_v6();",0,,"pqcomm.c",1516,
2026-11-17 11:28:41.828721 -03,"u_tfnvgx_aai_da_user","gpafiniti",p2073064,th-1662871360,"192.168.30.12","49346",2026-11-16 16:30:03 -03,871359,con10724,cmd5,seg-1,,dx5159336,x871359,sx1,"LOG","08006","could not send data to client: Broken pipe",,,,,,"SELECT applied_schema.vgx_tfn_sp_hourlyalert_v6();",0,,"pqcomm.c",1516,
2026-11-17 11:28:42.001519 -03,,,p9199,th-1662871360,,,,0,,,seg-1,,,,,"LOG","00000","background worker ""ic proxy process"" (PID 511961) exited with exit code 1",,,,,,,0,,"postmaster.c",4259,
Thanks for the report. This crash is a known bug in the resource queue code, and it is already fixed.
A session is waiting for a resource queue slot inside a subtransaction (after a SAVEPOINT). If it is terminated (for example with pg_terminate_backend()), the coordinator backend can fail with:
PANIC: We are trying to clean up a non-resource queue lock
That PANIC is the signal 6: Aborted in your log.
The fix is in commit 6994cfe21c3 ("Cancel resource queue wait before abort releases portals", #2095). It is included in 2.2.0-incubating but not in 2.0.0 or 2.1.0. Please upgrade to 2.2.0-incubating.
Activity
yjhjstz commentedon Nov 17, 2026
Hi @adnanhamdussalam,
Thanks for the report. This crash is a known bug in the resource queue code, and it is already fixed.
A session is waiting for a resource queue slot inside a subtransaction (after a
SAVEPOINT). If it is terminated (for example withpg_terminate_backend()), the coordinator backend can fail with:That PANIC is the
signal 6: Abortedin your log.The fix is in commit 6994cfe21c3 ("Cancel resource queue wait before abort releases portals", #2095). It is included in 2.2.0-incubating but not in 2.0.0 or 2.1.0. Please upgrade to 2.2.0-incubating.