In PostgreSQL, when a backend process crashes, it can cause other backend
processes to also require a restart, primarily to ensure data consistency. I
understand that the correct approach is to analyze and identify the cause of
the crash and resolve it. However, it is also important to be able to handle a
backend process crash without affecting the operation of other processes, thus
minimizing the scope of negative impact and improving availability. To achieve
this goal, could we mimic the Oracle process by introducing a "pmon" process
dedicated to rolling back crashed process transactions and performing resource
cleanup? I wonder if anyone has attempted such a strategy or if there have been
previous discussions on this topic.
