On 2025-Mar-07, Richard Guo wrote: > I encountered the same issue months ago and reported it here [1]. > Heikki suspected that commit 3c0fd64fec might be the culprit. > Unfortunately, we haven't been able to track it down because we > couldn't find a reliable way to reproduce it. One way to capture this might be to run the problem workload under rr enough times until it reproduces, and then it can then be replayed under the debugger. https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Recording_Postgres_using_rr_Record_and_Replay_Framework -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
pgsql-bugs by date:
Соглашаюсь с условиями обработки персональных данных