Re: Drop 32-bit support (was "Re: Fix typo 586/686 in atomics/arch-x86.h")

From: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Tomas Vondra <tv(at)fuzzy(dot)cz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Subject: Re: Drop 32-bit support (was "Re: Fix typo 586/686 in atomics/arch-x86.h")
Date: 2026-03-12 15:20:17
Message-ID: a5e58f96-dc9d-48b2-82df-49f6756ef5ff@postgrespro.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

12.03.2026 10:57, Jakub Wartak пишет:
> I propose simply for now that that if there's consensus to drop the 32-bits
> support, then in the release notes of PG19 we could simply add some
> deprecation notice/warning like "PostgreSQL 19 is _probably_ the last release
> to provide support for 32-bits architectures. Please consider planning upgrade
> to 64-bit architecture." (and this costs us nothing, and gives any potential
> user additional year, and project would have even freedom to continue for
> couple releases still with 32-bits until somebody develops proper patch).

imho, it is possible to declare last version with 32bit support as LTS.
i.e. support Pg18 or Pg19 for 10 years instead of 5 years.

I'd vote for Pg18 to be last 32bit aware :)))

--
regards
Yura Sokolov aka funny-falcon

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-03-12 15:27:32 Re: pg_stat_replication.*_lag sometimes shows NULL during active replication
Previous Message Tom Lane 2026-03-12 15:10:51 Re: Defend against -ffast-math in meson builds