Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u53lP-00BXkV-US for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2025 14:29:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1u53lN-00G1Pt-0i for pgsql-hackers@arkaria.postgresql.org; Wed, 16 Apr 2025 14:29:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1u53lM-00G1Pl-La for pgsql-hackers@lists.postgresql.org; Wed, 16 Apr 2025 14:29:17 +0000 Received: from mail.postgrespro.ru ([93.174.132.70]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u53lJ-000NvX-2S for pgsql-hackers@lists.postgresql.org; Wed, 16 Apr 2025 14:29:16 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1744813750; bh=a/fPy2lrAHNodvoBQQ9WISLRZE0mEijiCwfw1ONR24k=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=B9uT1pZZeyHug8LKsTtNHqqeHuSQsrY3uwQqFtqlv/gyiWv8ahbTMxzLbdVdoRkAl L05QclWImGHzkZ8paNH2oOaIRWsHQg/AIiEjgMVk4+H9cQDj3J6oI8pG+bsG9nvQt3 q+iAGWi706h8pGJOAPDaWnKy4C9nrtQWK2b+5d2f97ow/u/JeSPsfgriBxKGiVh/we jKbTan001D/SHuk8dT0G9AkIIVDbGHUoFIMXZfxmKPQchHnCJ4gJfJ7mX4nyhkhBSk lZy/b3nuFO4IPqKESy1qQP4L9NizTzrHbTf2cNw9jrKaGZofwswwsBRn2tt6k3UOU0 jQU32BqcWZHeQ== Received: from [192.168.27.71] (unknown [93.174.131.141]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: y.sokolov@postgrespro.ru) by mail.postgrespro.ru (Postfix/465) with ESMTPSA id 70986606E1; Wed, 16 Apr 2025 17:29:10 +0300 (MSK) Message-ID: Date: Wed, 16 Apr 2025 17:29:09 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Built-in Raft replication To: Andrey Borodin , Tom Lane Cc: Konstantin Osipov , Greg Sabino Mullane , Nikolay Samokhvalov , PostgreSQL Hackers References: <1798838.1744759182@sss.pgh.pa.us> <20FB597F-641F-48F8-8428-D8DDBA802D58@yandex-team.ru> <1832513.1744777613@sss.pgh.pa.us> <0ED408AD-2209-4D60-9142-B6D01DD0C46F@yandex-team.ru> Content-Language: en-US From: Yura Sokolov In-Reply-To: <0ED408AD-2209-4D60-9142-B6D01DD0C46F@yandex-team.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-KSMG-AntiPhishing: NotDetected X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 2.1.0.7854, bases: 2025/04/16 12:51:00 #27893531 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 16.04.2025 08:24, Andrey Borodin пишет: > 2. After failover, old Primary node must rejoin cluster by running pg_rewind and following timeline switch. It is really do-able: BiHA already does it. And BiHA runs as a child process of postmaster, ie both postmaster and BiHA doesn't restart when PostgreSQL needs to rewind and restart. Yes, there are non-trivial amount of changes made into postmaster machinery. But it is doable. -- regards Yura Sokolov aka funny-falcon