MIME-Version: 1.0
References: <Z_1Cq7JvabsFYjQo@ark>
 <CAKAnmmJxGHcQmzXqEQ-nppZjXyH7i5W_7Cz8JNMb2+6c5+D+og@mail.gmail.com>
 <CAM527d9+eGvdih1GxoPDJ2WYs6eitf39oNTxGxnCK1PgF=A8wg@mail.gmail.com>
 <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>
In-Reply-To: <0ED408AD-2209-4D60-9142-B6D01DD0C46F@yandex-team.ru>
From: Kirill Reshke <reshkekirill@gmail.com>
Date: Wed, 16 Apr 2025 10:39:07 +0500
Message-ID: 
 <CALdSSPhmEUT+2Wg7SMa3gnOetNiugtbd43pXDmcWJnfZti4LqA@mail.gmail.com>
Subject: Re: Built-in Raft replication
To: Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Konstantin Osipov <kostja.osipov@gmail.com>,
	Greg Sabino Mullane <htamfids@gmail.com>,
 Nikolay Samokhvalov <nik@postgres.ai>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CALdSSPhmEUT%2B2Wg7SMa3gnOetNiugtbd43pXDmcWJnfZti4LqA%40mail.gmail.com>
Precedence: bulk

On Wed, 16 Apr 2025 at 10:25, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
>
> I think I can provide some reasons why it cannot be neither extension, no=
r any part running within postmaster reign.
>
> 1. When joining cluster, there=E2=80=99s not PGDATA to run postmaster on =
top of it.

You can join the cluster on pg_basebackup of its master; So I dont get
why this is an anti-extension restriction.

> 2. After failover, old Primary node must rejoin cluster by running pg_rew=
ind and following timeline switch.

You can run bash from extension, what's the point?

> The system in hand must be able to manipulate with PGDATA without startin=
g Postgres.

--=20
Best regards,
Kirill Reshke