MIME-Version: 1.0
References: <20260302.094632.1950837561737687899.ishii@postgresql.org>
 <CAAAe_zCkpYn7qh=chxVLo4-HG8D57RwxhUq-c9zrYvZVtdDgeA@mail.gmail.com>
 <20260302.141823.129040280886273031.ishii@postgresql.org>
 <20260304.162450.1463961082114305353.ishii@postgresql.org>
In-Reply-To: <20260304.162450.1463961082114305353.ishii@postgresql.org>
Reply-To: assam258@gmail.com
From: Henson Choi <assam258@gmail.com>
Date: Wed, 4 Mar 2026 16:29:35 +0900
Message-ID: 
 <CAAAe_zAk3zRy4e=St-_7jqUB1cbw08B6-4Giwr+1Ei570J0byg@mail.gmail.com>
Subject: Re: Row pattern recognition
To: Tatsuo Ishii <ishii@postgresql.org>
Cc: vik@postgresfriends.org, er@xs4all.nl, jacob.champion@enterprisedb.com,
	david.g.johnston@gmail.com, peter@eisentraut.org,
	pgsql-hackers@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000d7bea1064c2dc819"
Archived-At: 
 <https://www.postgresql.org/message-id/CAAAe_zAk3zRy4e%3DSt-_7jqUB1cbw08B6-4Giwr%2B1Ei570J0byg%40mail.gmail.com>
Precedence: bulk

--000000000000d7bea1064c2dc819
Content-Type: text/plain; charset="UTF-8"

Hi Tatsuo,

CFBot complains v44-0007 patch corrupted.
> https://cfbot.cputube.org/patch_4460.log


I downloaded v44-0007 from the mailing list archive and applied it
successfully in my local environment. Everything works fine here.


> So it seems the file was truncated somwhere between me and PostgreSQL
> ML archiving.
>

It seems CFBot does not retry once it fails, so the initial truncation
error has become permanent.


> Can you check the size of the file attached to your mail?


I didn't check the raw attachment size, but the patch applied cleanly
without any issues.

To work around this, how about splitting the test patch (0007) into
separate patches for .sql and .out files? This would reduce the
individual file sizes and help avoid truncation during archiving.

Best regards,
Henson

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi Tatsuo,</div><div dir=3D"ltr"><br></di=
v><div class=3D"gmail_quote gmail_quote_container"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">CFBot c=
omplains v44-0007 patch corrupted.<br>
<a href=3D"https://cfbot.cputube.org/patch_4460.log" rel=3D"noreferrer" tar=
get=3D"_blank">https://cfbot.cputube.org/patch_4460.log</a></blockquote><di=
v><br></div><div>I downloaded v44-0007 from the mailing list archive and ap=
plied it<br>successfully in my local environment. Everything works fine her=
e.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left=
-color:rgb(204,204,204);padding-left:1ex">
So it seems the file was truncated somwhere between me and PostgreSQL<br>
ML archiving.<br></blockquote><div><br></div><div>It seems CFBot does not r=
etry once it fails, so the initial truncation<br>error has become permanent=
.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-l=
eft-color:rgb(204,204,204);padding-left:1ex">
Can you check the size of the file attached to your mail?</blockquote><div>=
<br></div>I didn&#39;t check the raw attachment size, but the patch applied=
 cleanly<br>without any issues.<br><br>To work around this, how about split=
ting the test patch (0007) into<br>separate patches for .sql and .out files=
? This would reduce the<br>individual file sizes and help avoid truncation =
during archiving.<br><br>Best regards,<br>Henson<br><div>=C2=A0</div></div>=
</div>

--000000000000d7bea1064c2dc819--