From: | Nikolay Samokhvalov <nik(at)postgres(dot)ai> |
---|---|
To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
Cc: | Konstantin Osipov <kostja(dot)osipov(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Built-in Raft replication |
Date: | 2025-04-15 22:27:56 |
Message-ID: | CAM527d9+eGvdih1GxoPDJ2WYs6eitf39oNTxGxnCK1PgF=A8wg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 15, 2025 at 8:08 AM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:
> On Mon, Apr 14, 2025 at 1:15 PM Konstantin Osipov <kostja(dot)osipov(at)gmail(dot)com>
> wrote:
>
>> If anyone is working on Raft already I'd be happy to discuss
>> the details. I am fairly new to the PostgreSQL hackers ecosystem
>> so cautious of starting work in isolation/knowing there is no
>> interest in accepting the feature into the trunk.
>>
>
> Putting aside the technical concerns about this specific idea, it's best
> to start by laying out a very detailed plan of what you would want to
> change, and what you see as the costs and benefits. It's also extremely
> helpful to think about developing this as an extension. If you get stuck
> due to extension limitations, propose additional hooks. If the hooks will
> not work, explain why.
>
This is exactly what I wanted to write as well. The idea is great. At the
same time, I think, consensus on many decisions will be extremely hard to
reach, so this project has a high risk of being very long. Unless it's an
extension, at least in the beginning.
Nik
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-04-15 22:51:55 | Re: pg_dump --if-exists --clean when drop index that is partition of a partitioned index |
Previous Message | Jelte Fennema-Nio | 2025-04-15 22:25:43 | Re: dispchar for oauth_client_secret |