MIME-Version: 1.0
References: <Z_1Cq7JvabsFYjQo@ark>
In-Reply-To: <Z_1Cq7JvabsFYjQo@ark>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Tue, 15 Apr 2025 11:07:42 -0400
Message-ID: 
 <CAKAnmmJxGHcQmzXqEQ-nppZjXyH7i5W_7Cz8JNMb2+6c5+D+og@mail.gmail.com>
Subject: Re: Built-in Raft replication
To: Konstantin Osipov <kostja.osipov@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000d8924f0632d289cc"
Archived-At: 
 <https://www.postgresql.org/message-id/CAKAnmmJxGHcQmzXqEQ-nppZjXyH7i5W_7Cz8JNMb2%2B6c5%2BD%2Bog%40mail.gmail.com>
Precedence: bulk

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

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

Getting this into core is going to be a long, multi-year effort, in which
people are going to be pushing back the entire time, so prepare yourself
for that. My immediate retort is going to be: why would we add this if
there are existing tools that already do the job just fine? Postgres has
lots of tasks that it is happy to let other programs/OS
subsystems/extensions/etc. handle instead.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

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

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Apr 14, 2025 at 1:15=E2=80=AFPM K=
onstantin Osipov &lt;<a href=3D"mailto:kostja.osipov@gmail.com">kostja.osip=
ov@gmail.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_cont=
ainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">If anyone is worki=
ng on Raft already 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><br></div><div>Getting this int=
o core is going to be a long, multi-year effort, in which people=C2=A0are g=
oing to be pushing back the entire time, so prepare yourself for that. My i=
mmediate retort is going to be: why would we add this if there are existing=
 tools that already do the job just fine? Postgres has lots of tasks that i=
t is happy to let other programs/OS subsystems/extensions/etc. handle inste=
ad.</div><div>=C2=A0</div></div><div dir=3D"ltr" class=3D"gmail_signature">=
<div dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><br></div><div>--</d=
iv><div>Crunchy Data - <a href=3D"https://www.crunchydata.com" target=3D"_b=
lank">https://www.crunchydata.com</a></div><div>Enterprise Postgres Softwar=
e Products &amp; Tech Support</div><div><br></div></div></div></div>

--000000000000d8924f0632d289cc--