MIME-Version: 1.0
References: <CACG=ezaWg7_nt-8ey4aKv2w9LcuLthHknwCawmBgEeTnJrJTcw@mail.gmail.com>
 <ff143b24-a093-40da-9833-d36b83726bdf@iki.fi> <CAGjGUAKO1GCzG5wBMt5RosWo0PatgFpYY=Gjgt77tN2brNe=Bg@mail.gmail.com>
 <CACG=ezYokoiumOFnqUfg_ffHD5s8T+6iHYfzKLfa=QQ-1pNrBg@mail.gmail.com>
 <CACG=ezY9xq73jcX_EjVqx5-f90nbQ9PyhFCTW2fwFCS2wmNiFw@mail.gmail.com>
 <CACG=eza+27CfLBobJJccRhXrA3He6c1irAnoyTtSC1-z9UXLrg@mail.gmail.com> <CAPpHfduczcop9s6gKUpLGgFUe2y4ERGMJx6SS6Kp+s-kQPwMjg@mail.gmail.com>
In-Reply-To: <CAPpHfduczcop9s6gKUpLGgFUe2y4ERGMJx6SS6Kp+s-kQPwMjg@mail.gmail.com>
From: Maxim Orlov <orlovmg@gmail.com>
Date: Wed, 4 Sep 2024 11:49:32 +0300
Message-ID: <CACG=ezbye4g_ERNqE=gBcvQ0YypRaVENhNUu8xrs4PL12UdnUA@mail.gmail.com>
Subject: Re: POC: make mxidoff 64 bits
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: wenhui qiu <qiuwenhuifx@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, 
	Postgres hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000006abb3b062147412c"
Archived-At: <https://www.postgresql.org/message-id/CACG%3Dezbye4g_ERNqE%3DgBcvQ0YypRaVENhNUu8xrs4PL12UdnUA%40mail.gmail.com>
Precedence: bulk

--0000000000006abb3b062147412c
Content-Type: text/plain; charset="UTF-8"

On Tue, 3 Sept 2024 at 16:32, Alexander Korotkov <aekorotkov@gmail.com>
wrote:

> I don't think you need to maintain CATALOG_VERSION_NO change in your
> patch for the exact reason you have mentioned: patch will get conflict
> each time CATALOG_VERSION_NO is advanced.  It's responsibility of
> committer to advance CATALOG_VERSION_NO when needed.
>

OK, I got it. My intention here was to help to test the patch. If someone
wants to have a
look at the patch, he won't need to make changes in the code. In the next
iteration, I'll
remove CATALOG_VERSION_NO version change.

-- 
Best regards,
Maxim Orlov.

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, 3 Sept 2024 at 16:32, Alexand=
er Korotkov &lt;<a href=3D"mailto:aekorotkov@gmail.com">aekorotkov@gmail.co=
m</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
I don&#39;t think you need to maintain CATALOG_VERSION_NO change in your<br=
>
patch for the exact reason you have mentioned: patch will get conflict<br>
each time CATALOG_VERSION_NO is advanced.=C2=A0 It&#39;s responsibility of<=
br>
committer to advance CATALOG_VERSION_NO when needed.<br></blockquote><div><=
br></div><div>OK, I got it. My intention here was to help to test the patch=
. If someone wants to have a=C2=A0</div><div>look at the patch, he won&#39;=
t need to make changes in the code. In the next iteration, I&#39;ll <br></d=
iv><div>remove CATALOG_VERSION_NO version change. </div><div>=C2=A0</div></=
div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" c=
lass=3D"gmail_signature"><div dir=3D"ltr"><div>Best regards,<br></div><div>=
Maxim Orlov.</div></div></div></div>

--0000000000006abb3b062147412c--