Re: Set huge_page_size on 32bit system

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: michael(at)paquier(dot)xyz
Cc: vilensipkdm(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Set huge_page_size on 32bit system
Date: 2026-06-26 08:13:07
Message-ID: 20260626.171307.1289242154888665760.horikyota.ntt@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

At Fri, 26 Jun 2026 14:26:31 +0900, Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-06-26 08:16:23 Re: Set huge_page_size on 32bit system
Previous Message Hüseyin Demir 2026-06-26 06:56:00 Re: BUG #19483: pg_upgrade fails with orphan records in pg_init_priv catalog table