MIME-Version: 1.0
References: 
 <CACeKOO2-14PPvBNeDn=Qf7X9OKu-WkyYxj0N61n9=60iz0QjFA@mail.gmail.com>
 <20250908.092628.942175382089863152.ishii@postgresql.org>
 <CACeKOO23dZSC6okH_YtChEb49YFLuJrwRxC7aVaHzbdX4-fZJA@mail.gmail.com>
 <20250909.093944.156562835222886259.ishii@postgresql.org>
In-Reply-To: <20250909.093944.156562835222886259.ishii@postgresql.org>
From: Nadav Shatz <nadav@tailorbrands.com>
Date: Mon, 15 Sep 2025 21:48:07 +0900
Message-ID: 
 <CACeKOO3QSDbwhg3NdFSAavcZ79H5VGR8=XCe4wsN4sCCyvoYVQ@mail.gmail.com>
Subject: Re: Proposal: recent access based routing for primary-replica setups
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: pgpool-hackers@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000064459063ed66bf7"
Archived-At: 
 <https://www.postgresql.org/message-id/CACeKOO3QSDbwhg3NdFSAavcZ79H5VGR8%3DXCe4wsN4sCCyvoYVQ%40mail.gmail.com>
Precedence: bulk

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

Hi Tatsuo,

Sorry for the late reply - I'm traveling with my family at the moment (in
Japan actually) and might be delayed in responding.

Re your points:
1 - we can, but I have to say that a user I tend to prefer configuration
values not have a "magic" value that does something different than the
usual case like this would create. I'd stick with what we already have
planned. happy to hear from others on the mailing list as well of course.

2 - I think we can have the primary always be the first or we can
completely remove it since it might be redundant as it's always going to be
0. what do you think?

3 - I agree with you, next version (after we clear everything else) will
have only ip/hostname+port.

Let me know your thoughts

Thanks!

On Tue, Sep 9, 2025 at 9:42=E2=80=AFAM Tatsuo Ishii <ishii@postgresql.org> =
wrote:

> Hi Nadav,
>
> > Hi Tatsuo,
> >
> > Please find attached the 3 patch files (implementation, tests, docs) wi=
th
> > the updates we discussed.
> >
> > What do you think?
>
> I haven't read the code details yet but I have a few questions.
>
> 1) Can we use only replication_delay_source_cmd and if it's value is
>    'builtin', then we treat it as replication_delay_source =3D builtin?
>    Maybe this is matter of taste but I would like to know your
>    opinion.
>
> 2) replication_delay_source_cmd will be given an ordered list of
>    instance identifiers. But it seems there's no way for the command
>    which one is the primary instance. Is it okay for the command?
>
> 3) Why do you have 3 kind of instance identifiers (application name,
>    hostname (IP) + port and node id? I thought "hostname (IP) + port"
>    is sufficient.
>
> Comments?
> --
> Tatsuo Ishii
> SRA OSS K.K.
> English: http://www.sraoss.co.jp/index_en/
> Japanese:http://www.sraoss.co.jp
>


--=20
Nadav Shatz
Tailor Brands | CTO

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

<div dir=3D"ltr">Hi=C2=A0Tatsuo,<div><br></div><div>Sorry for=C2=A0the late=
 reply - I&#39;m traveling with my family at the moment (in Japan actually)=
 and might=C2=A0be delayed in responding.</div><div><br></div><div>Re your =
points:</div><div>1 - we can, but I have to say that a user I tend to prefe=
r configuration values not have a &quot;magic&quot; value that does somethi=
ng different than the usual case like this would create. I&#39;d stick with=
 what we already have planned. happy to hear from others on the mailing lis=
t as well of course.</div><div><br></div><div>2 - I think we can have the p=
rimary always be the first or we can completely remove it since it might be=
 redundant as it&#39;s always going to be 0. what do you think?</div><div><=
br></div><div>3 - I agree with you, next version (after we clear everything=
 else) will have only ip/hostname+port.</div><div><br></div><div>Let me kno=
w your=C2=A0thoughts</div><div><br></div><div>Thanks!</div></div><br><div c=
lass=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_=
attr">On Tue, Sep 9, 2025 at 9:42=E2=80=AFAM Tatsuo Ishii &lt;<a href=3D"ma=
ilto:ishii@postgresql.org">ishii@postgresql.org</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">Hi Nadav,<br>
<br>
&gt; Hi Tatsuo,<br>
&gt; <br>
&gt; Please find attached the 3 patch files (implementation, tests, docs) w=
ith<br>
&gt; the updates we discussed.<br>
&gt; <br>
&gt; What do you think?<br>
<br>
I haven&#39;t read the code details yet but I have a few questions.<br>
<br>
1) Can we use only replication_delay_source_cmd and if it&#39;s value is<br=
>
=C2=A0 =C2=A0&#39;builtin&#39;, then we treat it as replication_delay_sourc=
e =3D builtin?<br>
=C2=A0 =C2=A0Maybe this is matter of taste but I would like to know your<br=
>
=C2=A0 =C2=A0opinion.<br>
<br>
2) replication_delay_source_cmd will be given an ordered list of<br>
=C2=A0 =C2=A0instance identifiers. But it seems there&#39;s no way for the =
command<br>
=C2=A0 =C2=A0which one is the primary instance. Is it okay for the command?=
<br>
<br>
3) Why do you have 3 kind of instance identifiers (application name,<br>
=C2=A0 =C2=A0hostname (IP) + port and node id? I thought &quot;hostname (IP=
) + port&quot;<br>
=C2=A0 =C2=A0is sufficient.<br>
<br>
Comments?<br>
--<br>
Tatsuo Ishii<br>
SRA OSS K.K.<br>
English: <a href=3D"http://www.sraoss.co.jp/index_en/" rel=3D"noreferrer" t=
arget=3D"_blank">http://www.sraoss.co.jp/index_en/</a><br>
Japanese:<a href=3D"http://www.sraoss.co.jp" rel=3D"noreferrer" target=3D"_=
blank">http://www.sraoss.co.jp</a><br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"rtl" class=3D"gmail_s=
ignature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div dir=3D"rtl"><div dir=
=3D"ltr"><font color=3D"#000000">Nadav Shatz</font></div><div dir=3D"ltr"><=
font color=3D"#000000">Tailor Brands=C2=A0| CTO</font></div></div></div></d=
iv></div></div>

--000000000000064459063ed66bf7--