Horton

Re: Remove non-fast promotion Re: Should we remove a fallback promotion? take 2

Jehan-Guillaume de Rorthais <jgdr@dalibo.com>

View thread View on postgr.es
From: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, ian.barwick@2ndquadrant.com, alvherre@2ndquadrant.com, michael@paquier.xyz, andres@anarazel.de, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org, cyberdemn@gmail.com
Date: 2020-04-22T18:56:41Z
Lists: pgsql-hackers 
On Wed, 22 Apr 2020 11:51:15 +0900
Fujii Masao <masao.fujii@oss.nttdata.com> wrote:

> On 2020/04/22 10:53, Kyotaro Horiguchi wrote:
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
> 
> Thanks all for checking whether the change affects each HA solution!

Unless I'm wrong, we don't have feedback from Patroni team.

I did some quick grep and it seems to rely on "pg_ctl promote" as well.
Moreover, the latest commit 80fbe9005 force a checkpoint right after the
promote. So I suppose they don't use non-fast promote.

I CC'ed Alexander Kukushkin to this discussion, so at least he is aware of
this topic.

Regards,

Commits

  1. Remove non-fast promotion.