MIME-Version: 1.0
References: <Z_1Cq7JvabsFYjQo@ark>
 <CAKAnmmJxGHcQmzXqEQ-nppZjXyH7i5W_7Cz8JNMb2+6c5+D+og@mail.gmail.com>
In-Reply-To: 
 <CAKAnmmJxGHcQmzXqEQ-nppZjXyH7i5W_7Cz8JNMb2+6c5+D+og@mail.gmail.com>
From: Nikolay Samokhvalov <nik@postgres.ai>
Date: Tue, 15 Apr 2025 15:27:56 -0700
Message-ID: 
 <CAM527d9+eGvdih1GxoPDJ2WYs6eitf39oNTxGxnCK1PgF=A8wg@mail.gmail.com>
Subject: Re: Built-in Raft replication
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: Konstantin Osipov <kostja.osipov@gmail.com>,
 pgsql-hackers@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000e432ab0632d8ae00"
Archived-At: 
 <https://www.postgresql.org/message-id/CAM527d9%2BeGvdih1GxoPDJ2WYs6eitf39oNTxGxnCK1PgF%3DA8wg%40mail.gmail.com>
Precedence: bulk

--000000000000e432ab0632d8ae00
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 15, 2025 at 8:08=E2=80=AFAM Greg Sabino Mullane <htamfids@gmail=
.com>
wrote:

> On Mon, Apr 14, 2025 at 1:15=E2=80=AFPM Konstantin Osipov <kostja.osipov@=
gmail.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

--000000000000e432ab0632d8ae00
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>On Tue, Apr 15, 2025 at 8:08=E2=80=
=AFAM Greg Sabino Mullane &lt;<a href=3D"mailto:htamfids@gmail.com">htamfid=
s@gmail.com</a>&gt; wrote:</div></div><div class=3D"gmail_quote gmail_quote=
_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr"><div dir=3D"ltr">On Mon, Apr 14, 2025 at 1:15=E2=80=AFPM Konstantin Osi=
pov &lt;<a href=3D"mailto:kostja.osipov@gmail.com" target=3D"_blank">kostja=
.osipov@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">If anyone is working on Raft alread=
y I&#39;d be happy to discuss<br>
the details. I am fairly new to the PostgreSQL hackers ecosystem<br>
so cautious of starting work in isolation/knowing there is no<br>
interest in accepting the feature into the trunk.<br></blockquote><div><br>=
</div><div>Putting aside the technical concerns about=C2=A0this specific id=
ea, it&#39;s best to start by laying out a very detailed plan of what you w=
ould want to change, and what you see as the costs and benefits. It&#39;s a=
lso extremely helpful to think about developing this as an extension. If yo=
u get stuck due to extension limitations, propose additional hooks. If the =
hooks will not work, explain why.</div></div></div></blockquote><div><br></=
div><div>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 h=
ard to reach, so this project has a high risk of being very long. Unless it=
&#39;s an extension, at least in the beginning.</div><div><br></div><div>Ni=
k</div></div></div>

--000000000000e432ab0632d8ae00--