From: | Konstantin Osipov <kostja(dot)osipov(at)gmail(dot)com> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | Kirill Reshke <reshkekirill(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 10:02:00 |
Message-ID: | Z_-AGO5sQQ03JGNx@ark |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Andrey Borodin <x4mmm(at)yandex-team(dot)ru> [25/04/16 11:06]:
> > You can run bash from extension, what's the point?
>
> You cannot run bash that will stop backend running bash.
You're right there is a chicken and egg problem when you add
Raft to an existing project, and rebootstrap
becomes a trick, but it's a plumbing trick.
The new member needs to generate and persist a globally unique
identifier as the first step. Later it can
reintroduce itself to the cluster given this identifier
can be preserved in the new incarnation (popen + fork).
--
Konstantin Osipov, Moscow, Russia
From | Date | Subject | |
---|---|---|---|
Next Message | Maxim Orlov | 2025-04-16 11:04:53 | POC: Parallel processing of indexes in autovacuum |
Previous Message | Konstantin Osipov | 2025-04-16 09:58:32 | Re: Built-in Raft replication |