Horton

Re: Add Information during standby recovery conflicts

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

View thread View on postgr.es
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: sawada.mshk@gmail.com
Cc: masao.fujii@oss.nttdata.com, bdrouvot@amazon.com, alvherre@alvh.no-ip.org, masahiko.sawada@2ndquadrant.com, pgsql-hackers@postgresql.org
Date: 2020-12-16T05:54:22Z
Lists: pgsql-hackers 
At Wed, 16 Dec 2020 14:49:25 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
> > > > Conflicting processes are 41171, 41194.
> > > > Conflicting processes are: 41171, 41194.
> 
> Or I came up with the following after scanning throught the tree.
> 
> | Some processes are conflicting: 41171, 41194.

Or

Some processes are blocking recovery progress: 41171, 41194.

?

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Commits

  1. Log long wait time on recovery conflict when it's resolved.

  2. Add GUC to log long wait times on recovery conflicts.

  3. Detect the deadlocks between backends and the startup process.

  4. Get rid of the dedicated latch for signaling the startup process.

  5. Add block information in error context of WAL REDO apply loop