| From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Konstantin Osipov <kostja(dot)osipov(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Built-in Raft replication |
| Date: | 2025-04-16 05:39:07 |
| Message-ID: | CALdSSPhmEUT+2Wg7SMa3gnOetNiugtbd43pXDmcWJnfZti4LqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 16 Apr 2025 at 10:25, Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
>
> I think I can provide some reasons why it cannot be neither extension, nor any part running within postmaster reign.
>
> 1. When joining cluster, there’s 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_rewind 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 starting Postgres.
--
Best regards,
Kirill Reshke
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2025-04-16 05:44:13 | Re: Built-in Raft replication |
| Previous Message | Andrey Borodin | 2025-04-16 05:24:48 | Re: Built-in Raft replication |