How to solve the problem of one backend process crashing and causing other processes to restart?

From: yuansong <yyuansong(at)126(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: How to solve the problem of one backend process crashing and causing other processes to restart?
Date: 2023-11-13 02:30:44
Message-ID: 37b7a067.1773.18bc68459d2.Coremail.yyuansong@126.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-11-13 02:38:34 Re: [EXTERNAL] Re: Add non-blocking version of PQcancel
Previous Message Zhijie Hou (Fujitsu) 2023-11-13 00:49:28 RE: Synchronizing slots from primary to standby