MIME-Version: 1.0
References: 
 <CAMp4U1d177Jf9ZJwXGKom6APx3LSFATa=Z-M=N5kLzvTUcxutw@mail.gmail.com>
 <20260626.132415.904994526137946499.horikyota.ntt@gmail.com>
 <aj4Nh0a9WiZXAjA5@paquier.xyz>
 <20260626.171307.1289242154888665760.horikyota.ntt@gmail.com>
 <aj41V5ACiv9OfkIF@paquier.xyz> <aj86XQUWLOqOrMrS@paquier.xyz>
In-Reply-To: <aj86XQUWLOqOrMrS@paquier.xyz>
From: Daria Shanina <vilensipkdm@gmail.com>
Date: Tue, 30 Jun 2026 16:23:59 +0300
Message-ID: 
 <CAMp4U1cvurfHJQCEn1VtK0YhELjkywJ+ohZRV0SCG4VvNe84AA@mail.gmail.com>
Subject: Re: Set huge_page_size on 32bit system
To: Michael Paquier <michael@paquier.xyz>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>,
 pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000d3a0bf0655788e9a"
Archived-At: 
 <https://www.postgresql.org/message-id/CAMp4U1cvurfHJQCEn1VtK0YhELjkywJ%2BohZRV0SCG4VvNe84AA%40mail.gmail.com>
Precedence: bulk

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

Hello,
Kiyotaro and Michael, thank you so much for your answers!
Using MAX_KILOBYTES as the upper bound is indeed absolutely accurate, and
now everything is working correctly.

---
Best regards,
Daria Shanina

=D1=81=D0=B1, 27 =D0=B8=D1=8E=D0=BD. 2026=E2=80=AF=D0=B3. =D0=B2 05:50, Mic=
hael Paquier <michael@paquier.xyz>:

> On Fri, Jun 26, 2026 at 05:16:23PM +0900, Michael Paquier wrote:
> > Changing the states of the GUC tables in the stable branches would be
> > OK in this case.  Now, it took so many years for somebody to complain
> > that setting huge pages at 1TB on a 32b build does not work that I
> > cannot really get excited about a backpatch.  So I would just do the
> > switch on HEAD, and call it a day.
>
> And just applied a patch doing so, HEAD-only.
> --
> Michael
>


--=20
=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,
=D0=A8=D0=B0=D0=BD=D0=B8=D0=BD=D0=B0 =D0=94=D0=B0=D1=80=D1=8C=D1=8F =D0=90=
=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=80=D0=BE=D0=B2=D0=BD=D0=B0

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

<div dir=3D"ltr">Hello,<br>Kiyotaro and Michael, thank you so much for your=
 answers!<br>Using MAX_KILOBYTES as the upper bound is indeed absolutely ac=
curate, and now everything is working correctly.<br><br>---<br>Best regards=
,<br>Daria Shanina</div><br><div class=3D"gmail_quote gmail_quote_container=
"><div dir=3D"ltr" class=3D"gmail_attr">=D1=81=D0=B1, 27 =D0=B8=D1=8E=D0=BD=
. 2026=E2=80=AF=D0=B3. =D0=B2 05:50, Michael Paquier &lt;<a href=3D"mailto:=
michael@paquier.xyz">michael@paquier.xyz</a>&gt;:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">On Fri, Jun 26, 2026 at 05:16:23PM +0900,=
 Michael Paquier wrote:<br>
&gt; Changing the states of the GUC tables in the stable branches would be<=
br>
&gt; OK in this case.=C2=A0 Now, it took so many years for somebody to comp=
lain<br>
&gt; that setting huge pages at 1TB on a 32b build does not work that I<br>
&gt; cannot really get excited about a backpatch.=C2=A0 So I would just do =
the<br>
&gt; switch on HEAD, and call it a day.<br>
<br>
And just applied a patch doing so, HEAD-only.<br>
--<br>
Michael<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span class=
=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_s=
ignature"><div dir=3D"ltr">=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=
=B8=D0=B5=D0=BC,<div>=D0=A8=D0=B0=D0=BD=D0=B8=D0=BD=D0=B0 =D0=94=D0=B0=D1=
=80=D1=8C=D1=8F =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B0=D0=BD=D0=B4=D1=80=D0=
=BE=D0=B2=D0=BD=D0=B0</div></div></div>

--000000000000d3a0bf0655788e9a--