Horton

Re: Set huge_page_size on 32bit system

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

View thread View on postgr.es
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: michael@paquier.xyz
Cc: vilensipkdm@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2026-06-26T08:13:07Z
Lists: pgsql-bugs 
At Fri, 26 Jun 2026 14:26:31 +0900, Michael Paquier <michael@paquier.xyz> wrote in 
> So it seems to me that the mistake is that huge_page_size uses INT_MAX
> as upper bound.  We should use MAX_KILOBYTES instead; this definition
> exists to exactly prevent this kind of computation mistake in 32b
> environments.

Ah, you're right. MAX_KILOBYTES exists for exactly this purpose.

Regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Commits

  1. Switch maximum of GUC huge_page_size to MAX_KILOBYTES